# Ghost Protocol

> Use this tool when you need to manage MCP directory submissions and track listing readiness for agent/tool directories, solving problems related to agent discovery and pricing requirements. It provides a canonical submission packet with specific URLs for MCP endpoints, metadata, and manifests, and offers tools like `list_agents` and `get_payment_requirements` with a read-only interface. Use it in contexts where automated monitoring and verification of MCP servers are necessary.

Canonical page: https://skillsregistry.net/skills/ghostprotocol-readonly-mcp  
JSON: https://api.skillsregistry.net/v1/skills/ghostprotocol-readonly-mcp

## Description

# MCP Directory Submissions

This page tracks Ghost Protocol MCP listing readiness for agent/tool directories.

## Submission packet (canonical)

Use these URLs in every directory submission:

- MCP endpoint: `https://ghostprotocol.cc/api/mcp/read-only`
- MCP metadata: `https://ghostprotocol.cc/api/mcp/read-only` (`GET`)
- MCP manifest: `https://ghostprotocol.cc/.well-known/mcp.json`
- OpenAPI: `https://ghostprotocol.cc/openapi.json`
- LLM index: `https://ghostprotocol.cc/llms.txt`
- AI plugin manifest: `https://ghostprotocol.cc/.well-known/ai-plugin.json`
- Pricing endpoint: `https://ghostprotocol.cc/api/pricing`
- Terms: `https://ghostprotocol.cc/terms`
- Privacy: `https://ghostprotocol.cc/privacy`

Tool list:

- `list_agents`
- `get_agent_details`
- `get_payment_requirements`

Scope statement:

- "Read-only MCP server for agent discovery and pricing requirements. No settlement, ticket issuance, wallet actions, or state mutation."

## Directory targets

Status meanings:
- `READY`: packet complete and endpoint live.
- `SUBMIT`: requires manual external listing submission.
- `LISTED`: public listing confirmed.

| Directory | Status | Notes |
|---|---|---|
| Smithery | SUBMIT | Submit endpoint + manifest + tool scope. |
| MCP.so | SUBMIT | Submit server profile and canonical endpoint. |
| mcpservers.org | SUBMIT | Submit public metadata and capability summary. |
| Cursor directory (if/when open) | SUBMIT | Use same packet above. |

Copy-ready listing profile:

- `docs/developer-portal/mcp-submission-profile.md`

## Verification checklist before each submission

1. `GET /api/mcp/read-only` returns `ok: true` and expected tool list.
2. `POST /api/mcp/read-only` with `tools/list` returns 200 and tool schema.
3. `/.well-known/mcp.json` resolves and matches live endpoint URL.
4. `openapi.json` and `llms.txt` are reachable from production.

## Automated monitoring

Workflow:

- `.github/workflows/mcp-readonly-monitor.yml`

Schedule:

- Twice per hour (`:17` and `:47`, UTC)

It verifies:

1. `GET /api/mcp/read-only`
2. `GET /.well-known/mcp.json`
3. MCP JSON-RPC `initialize`
4. MCP JSON-RPC `tools/list`
5. MCP JSON-RPC `tools/call` for:
   - `list_agents`
   - `get_payment_requirements`

## Trust

- **Trust score (0–1):** 0.50
- **Verification tier:** unverified

## Facts

- **Version:** 1.0.0
- **Skill type:** atomic
- **Execution layer:** mcp-remote
- **Runtime environment:** api
- **Category:** version-control
- **Updated:** 2026-05-12

## Source

- **Source listing:** [Smithery](https://smithery.ai/server/ghostprotocol/readonly-mcp)

## Use it

Resolve this record through the SkillsRegistry MCP server (no auth, read-only):

```
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp
```

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_skill",
    "arguments": {
      "slug": "ghostprotocol-readonly-mcp"
    }
  }
}
```

REST: `GET https://api.skillsregistry.net/v1/skills/ghostprotocol-readonly-mcp` · pull for local use: `GET https://api.skillsregistry.net/v1/skills/ghostprotocol-readonly-mcp/pull`

---
SkillsRegistry indexes agent skills from public registries and GitHub. Skills we have analysed are scanned with Circle-IR and scored on six dimensions; each listing states its scan coverage. More: https://skillsregistry.net/llms.txt