Locus Protocol (Gryd.world)

world.grydPublished by gryd.worldOfficial publisherv1.1.0Updated Oct 24, 2026

Read/verify the public map of location-anchored BSV pins; build place/mint payloads. No auth.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP endpoint for reading and verifying a public map of location-anchored BSV pins and building place or mint payloads, with no authentication.

What you can do
Read and verify the public map of location-anchored BSV pins, checking what is recorded at a location and whether it holds up. Build place payloads for location-anchored entries. Build mint payloads for creating new pins. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to look up or verify location-anchored BSV pins on a public map, or to prepare place and mint payloads before they are submitted elsewhere. It is not aimed at general mapping, routing or private data work.
Requirements
A remote streamable HTTP connection to the provider's endpoint; no package, runtime, account, API key or header is declared. Network access to the provider is required.
Before you install
The server builds mint payloads, which relate to creating pins; confirm what happens to those payloads and whether any on-chain or paid action follows before using them. The map is described as public, so treat anything read or prepared as visible. No authentication is declared, so do not send secrets or private data.

Installation

In SourceWeft

  1. Open Locus Protocol (Gryd.world) in the dashboard and add it to a workspace.
  2. 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/world.gryd%2Flocus/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.

{
  "mcpServers": {
    "locus-protocol-gryd-world": {
      "type": "http",
      "url": "https://gryd.world/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestOct 15, 2026

Score

56% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.