Reported issues for mcp

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to mcp.

Most discussed

Harden the release pipeline

Two small guards on the release path.

Leak scan in CI This is a public repository. Add a check that fails on internal hostnames, service names and local paths, so nothing slips in through a tool description or a doc edit.

Optional release gate A production environment with a v* tag rule would put a human approval in front of publishing. Deliberately not required today, so releases are not blocked on it.

Note for whoever configures it: the release workflow triggers on a tag, and a

Read the thread · 2026-08-04 · closed · 1 comment

Add an eval harness for tool quality

Tool descriptions and schemas should be changed against measurements, not intuition.

Harness

• Realistic multi-step tasks against realistic data, with verifiable outcomes
• Record per run: accuracy, total tool calls, total tokens, error counts
• Keep a held-out set

What it should catch

• Redundant calls, which mean the pagination defaults are wrong
• Invalid-argument errors, which mean a description is unclear
• Tool selection drifting as the catalogue grows

Published guidance puts to

Read the thread · 2026-08-04 · closed · 1 comment

Document the MCP server publicly

There is no public documentation for the MCP server yet.

Scope

• A docs page covering install, configuration, the tool list, and the Auto flow
• Generate the tool table from manifest.json rather than writing it by hand, so it cannot drift from the server
• Cross-link from the agent skill, one line: MCP is the surface for clients that have no shell

Why generated The README table is already produced from manifest.json by npm run docs:tools, and CI fails if it goes stale. The docs p

Read the thread · 2026-08-04 · closed · 1 comment

Publish to the MCP Registry

List the server in the official MCP Registry so it shows up in client directories and aggregators.

server.json is already written and versioned alongside the package.

Steps

• Claim the ai.elfa namespace by proving domain ownership — a DNS TXT record on elfa.ai, or /.well-known/mcp-registry-auth
• mcp-publisher init / login / publish
• Confirm mcpName in package.json still matches name in server.json (CI already fails if the versions drift)

Notes

• The registry is

Read the thread · 2026-08-04 · closed · 1 comment

Hosted read-only Streamable HTTP endpoint is not deployed

The server already speaks Streamable HTTP. It is stateless, ships in the package, and is covered by tests — it is simply not deployed anywhere.

ELFA_MCP_TRANSPORT=http ELFA_MCP_PORT=3000 npx -y @elfa-ai/mcp

Scope: read-only

The hosted endpoint exposes the read tools only. Auto writes and exchange linking stay on stdio, where the signing secret already lives in the user's own environment.

That settles the one design question. The signing secret is issued per user, so a multi-te

Read the thread · 2026-08-04 · open · 0 comments

Ship a desktop bundle and one-click install links

npx works today. Add the lower-friction install paths.

MCPB bundle

• Single-click install and auto-update in Claude Desktop
• mcpb init / mcpb pack, published as a release asset

One-click links

• Cursor and VS Code deeplinks in the README, so install is a button rather than a JSON edit

Both are packaging only; no server changes.

Read the thread · 2026-08-04 · closed · 0 comments

Most recent

The remaining reports are on the project's issue tracker.