Model Context Protocol

Connect an AI Agent to MiddleVerse

MiddleVerse runs a real, live MCP server. Any MCP-compatible agent — Claude, a Meta agent, a custom client — can connect today with no account and no API key for read access.

Connection details

Endpoint: https://middleverse.ai/mcp
Transport: JSON-RPC 2.0 over HTTP POST
Protocol version: 2024-11-05
Server name: middleverse-directory

Authentication

Every read tool below works with no login, no API key, and no request headers — search and lookups are open to any agent. book_business is the only tool that requires an agent key, sent via the same header the REST booking API uses. Read-only agents never need to authenticate at all.

Live tools (8)

search_businesses

None

Search the directory by category, canonical attribute key, location, or keywords.

get_business

None

Get full details for a specific business by its slug or name, including canonical known attributes.

get_directory_stats

None

Get public directory totals — Verified/Unverified counts, category and location coverage, crawl-feed URLs.

list_businesses

None

List every public business through stable pagination, with Verified/Unverified status.

list_directory_categories

None

List public directory categories with business counts through stable pagination.

check_availability

None

Check booking availability for a business — whether it accepts bookings, which path, and the booking URL or contact method.

find_by_category_location

None

Natural-language lookup, e.g. "find a plumber near Cle Elum" — returns top-rated, booking-aware results.

book_business

Agent key required

Create a confirmed booking request after explicit customer confirmation. Requires a unique idempotency_key; refuses businesses without an owner claim, enabled booking, and a real available slot.

A ninth tool, send_inquiry, becomes available per business when that business is verified and has a public contact email — it emails the business directly and never requires authentication either.

How to connect

Send a standard MCP initialize call, then list the tools. Both are plain JSON-RPC POSTs — no SDK required, though any MCP client library will do this for you automatically.

curl -X POST https://middleverse.ai/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

curl -X POST https://middleverse.ai/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

curl -X POST https://middleverse.ai/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{
        "name":"find_by_category_location",
        "arguments":{"category":"restaurant","location":"Leavenworth WA"}
      }}'

Discovery endpoints

GET

/mcp

Discovery document: server info, protocol version, and the tool list.

POST

/mcp

JSON-RPC 2.0 endpoint. Handles initialize, tools/list, and tools/call.

GET

/.well-known/mcp

Same discovery document at the MCP well-known path.

GET

/openapi.json

Full OpenAPI specification for the REST API.

GET

/.well-known/ai-plugin.json

Plugin manifest for platforms that consume that format.

GET

/llms.txt

Plain-text summary for LLMs that read llms.txt before anything else.