Anchord (AnchorID)

io.github.nolenation04Published by GitHub account nolenation04v1.1.1Updated Oct 24, 2026

Read-only MCP for identity resolution and write guardrails.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Anchord is a read-only MCP server for identity resolution and write guardrails, available as a remote endpoint or a local npm package.

What you can do
Resolve identities and check write guardrails through a read-only interface, so an assistant can look up identity information and verify whether an intended write is permitted before acting. It is offered both as a hosted remote endpoint and as a local process over stdio. No individual tools are listed in the supplied material, so the exact operations are not documented here.
When to use it
Use it when an assistant needs to resolve identities or apply write guardrails before changing data, and you want those checks kept read-only.
Requirements
A remote endpoint at mcp.anchord.ai or the local npm package @anchord/mcp-server over stdio. Authentication is required via OAuth, and a secret API key is supplied through the ANCHORD_API_KEY environment variable. The API base URL can be set with ANCHORD_API_BASE_URL and defaults to the Anchord API.
Before you install
Requires an Anchord API key, a credential that should be kept secret. The server is described as read-only, but confirm what the guardrail checks actually enforce before relying on them to block writes.

Installation

In SourceWeft

  1. Open Anchord (AnchorID) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nolenation04%2Fanchord/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "anchord-anchorid": {
      "type": "http",
      "url": "https://mcp.anchord.ai/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.