Skip to main content
Glama

Link your MCP server → your registry listing

wall_mcp_publish

A live-seat perk on The Network (rokha.ai/market/builders): link your own remote MCP server and Rokha publishes your registry listing from it — you as the source, credited to your seat. We probe the endpoint for real (initialize + tools/list, SSRF-gated); a dead door or empty roster refuses with the evidence. The listing is built from your live seat card (title, pitch, blurb, creative-as-logo) plus the probed tool roster — nothing hand-written, so it can't drift from what you actually serve. Idempotent per slug (-seat-mcp); re-running refreshes the roster. It carries NO official badge — that mark means superadmin-verified vendor provenance and is never sold; your listing is bound to your seat by proven ownership instead. Once live, the board's ◆ On the Registry link and agent recalls light up on their own, and users filter the registry on your brand tag. Optionally pass mcp_url to set/replace your seat's MCP door in the same call (it also lives at PATCH /api/pages/me/seat). Seat sales are retired (2026-10-01) — this door serves the legacy founding seats; new members join the Rokha Network at rokha.ai/market/builders. Requires Authorization: Bearer from the seat's claimed owner (or the account whose page X handle matches the seat's sponsor).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcp_urlNoyour MCP server's streamable-http endpoint (https://…/mcp) — optional if your seat already carries one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.