Hosted MCP server/Other

DechoNet MCP server

Hosted at dechonet.com·Streamable HTTP

DechoNet gives an agent domain security reconnaissance tools. It covers DNS and domain records, security signals and related checks used in an assessment. The basic remote endpoint at https://dechonet.com/mcp is URL-only and needs no API key; an optional API key adds account limits and the infrastructure_pivot tool. The provider documents the remote setup in the dechonet-mcp repository.

dechonet.com Streamable HTTP No key for the basic remote endpoint; optional API key for account limits and infrastructure_pivot Server not checked yet Reviewed 2026-11-16
About

Where it fits

Security researchers and IT teams that want quick domain reconnaissance from an assistant.

  • Check a domain's DNS and security records.
  • Review related domain signals for an assessment.
  • Use infrastructure_pivot with an API key for deeper infrastructure mapping.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds DechoNet as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http dechonet https://dechonet.com/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://dechonet.com/mcp
Host
dechonet.com · /mcp
Transport
Streamable HTTP
Authentication
No key for the basic remote endpoint; optional API key for account limits and infrastructure_pivot
Server name
dechonet
Listing type
Community or directory listing

The installer uses the server name dechonet. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that dechonet appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Check a domain's DNS and security records. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

DechoNet repositoryhttps://github.com/node-man/dechonet-mcp