Skip to content

The MW Desk Data Center API MCP server

com.themwdesk/data-centerthemwdesk.comstreamable-httpv1.0.0Scanned

Paid US data center API: projects, county power, deals and legislation from public sources.

6 tools: 6 change things.

Tools: 0 delete, 0 irreversible, 6 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the The MW Desk Data Center API MCP server can do

The The MW Desk Data Center API MCP server is published by themwdesk.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (6 tools: dc_projects, dc_power, dc_deals, dc_legislation and 2 more), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 6Claude Code: ask
  • dc_dealsData center M&A, leasing and financing deals with public price and $/MW where disclosed, with sources.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Data center M&A, leasing and financing deals with public price and $/MW where disclosed, with sources. Filters: market, limit (max 50). Costs 3 credits ($0.03) per call; needs an API key.
  • dc_legislationData center bills, ordinances and moratoriums with status and next action, with sources.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Data center bills, ordinances and moratoriums with status and next action, with sources. Filters: state, limit (max 50). Costs 1 credits ($0.01) per call; needs an API key.
  • dc_powerPower and siting context by county: project count, known MW, power status mix, utilities, opposition count, sources.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Power and siting context by county: project count, known MW, power status mix, utilities, opposition count, sources. Filters: state, county, limit (max 50). Costs 1 credits ($0.01) per call; needs an API key.
  • dc_pricingFree: prices per tool and how to buy credits.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Free: prices per tool and how to buy credits.
  • dc_projectsUS data center projects from public sources: MW, stage, power status, utility, opposition, source URLs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    US data center projects from public sources: MW, stage, power status, utility, opposition, source URLs. Filters: state (2-letter), county, stage, min_mw, limit (max 50). Costs 2 credits ($0.02) per call; needs an API key.
  • dc_sampleFree: three example rows from each paid tool so you can see the data shape before buying credits.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Free: three example rows from each paid tool so you can see the data shape before buying credits.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://themwdesk.com/mcp: tools/list returned 6 tools to an anonymous client, including dc_projects (write), dc_power (write), dc_deals (write), dc_legislation (write), dc_sample (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http data-center https://themwdesk.com/mcp
claude mcp add --transport http data-center https://themwdesk.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__data-center__dc_projects",
      "mcp__data-center__dc_power",
      "mcp__data-center__dc_deals",
      "mcp__data-center__dc_legislation",
      "mcp__data-center__dc_sample",
      "mcp__data-center__dc_pricing"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as data-center. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.themwdesk/data-center/verify?hash=0cf8b2aa0d9b9dc6a576ebc8353bf90461cd10757cca45c4a819c403be62c12b" | jq -e '.changed == false'

Pinned hash 0cf8b2aa0d9b, from Nov 18, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.themwdesk/data-center/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.themwdesk/data-center
[![Anlyon Radar](https://radar.anlyon.com/badge/com.themwdesk/data-center.svg)](https://radar.anlyon.com/servers/com.themwdesk/data-center)

Source: MCP Registry. Synced Nov 18, 2026, 23:17 UTC.

The MW Desk Data Center API MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the The MW Desk Data Center API MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the The MW Desk Data Center API MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the The MW Desk Data Center API MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the The MW Desk Data Center API MCP server have?

6 tools: 6 write. dc_projects, dc_power, dc_deals, dc_legislation, dc_sample and dc_pricing.

Does the The MW Desk Data Center API MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the The MW Desk Data Center API MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the The MW Desk Data Center API MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.