---
title: "Mcp Server Card"
method: GET
path: "/.well-known/mcp/server-card.json"
---

# Mcp Server Card

`GET /.well-known/mcp/server-card.json`

## Request

- Base URL: `https://www.oxfordledge.com` (the document declares no server; this is the origin it was published from)
- URL: `https://www.oxfordledge.com/.well-known/mcp/server-card.json`
- Auth: none declared

AGENT-3 (SEP-1649): the MCP server card — a machine-readable descriptor an agent reads to
discover + install this site's MCP server. Modeled on the MCP registry server.json shape
(name / description / version / packages+transport), so it validates against tooling that
already understands that schema, plus an Oxford-Ledge `_meta` block for the tool count +
catalog links.

Truthful by construction: the server is a STDIO server distributed as the PyPI package
`oxford-ledge-mcp` — and, since the 2026-08 streamable transport shipped, ALSO a live
remote Streamable-HTTP endpoint at POST /mcp, advertised in `remotes` below. (An earlier
revision of this docstring said "there is NO remote endpoint" — that predated
routes_mcp_public_fastapi and had itself become the citable wrong answer this card
exists to avoid; 2026-08-24 MCP audit.) The tool count is
computed from the live tool-definition list (not a hard-coded literal — the stale "36 tools"
string elsewhere is exactly the drift this avoids). Transport auth is none; per-tool tier
gates are enforced via the OXFORD_LEDGE_USER_TIER env var the client sets.

## Response `200`

Successful Response

- unknown

---

[API](https://skmtc.dev/oxfordledge/apis/oxford-ledge-api.md) · [All operations](https://skmtc.dev/oxfordledge/apis/oxford-ledge-api/llms.txt) · [OpenAPI document](https://skmtc.dev/oxfordledge/apis/oxford-ledge-api/revisions/e832a1260f0b?raw)