Sourcey MCP Server
Official# Sourcey MCP Server
Find evidence-backed startup credits and deals, inspect Agent Readiness report cards, and
prepare canonical service declarations from an agent client.
Sourcey is already a hosted Streamable HTTP MCP server:
```text
https://mcp.sourcey.com/mcp
```
Use that URL directly when your client supports remote MCP. This package is the thin stdio
bridge for clients that require a local command:
```bash
npx -y @sourcey/mcp-server
```
```json
{
"mcpServers": {
"sourcey": {
"command": "npx",
"args": ["-y", "@sourcey/mcp-server"]
}
}
}
```
The bridge downloads no Catalog and contains no tool implementations. At startup it negotiates
with the live Sourcey server, reads the current tool definitions once, and relays tool calls. A
Catalog or tool-description update therefore needs no package release.
## What agents can do
- search and compare current startup credits, discounts, free tiers, programs, perks, and deals;
- inspect exact evidence, freshness, eligibility unknowns, and the signed change feed;
- search and inspect Agent Readiness report cards, including visible grades, five-stage findings,
blockers, remediations, methods, coverage, and freshness;
- prepare canonical Agent Readiness declaration YAML without assigning a grade; and
- discover Sourcey's paid HTTP services and x402 endpoint without paying inside MCP.
Call `tools/list` for the exact live schemas and descriptions. Sourcey's full agent guide is at
[sourcey.com/SKILL.md](https://sourcey.com/SKILL.md), its OpenAPI contract is at
[api.sourcey.com/openapi.yml](https://api.sourcey.com/openapi.yml), and x402 discovery is at
[api.sourcey.com/.well-known/x402](https://api.sourcey.com/.well-known/x402).
## Boundary
This package performs only two actions: MCP over local stdio and MCP over the configured hosted
HTTP endpoint. It has no wallet, payment signer, credentials, telemetry, browser, background
daemon, mutable plugin, Catalog data, Agent Readiness executor, or submission authority. Paid
work remains on Sourcey's canonical HTTP API.
`SOURCEY_MCP_URL` may select another HTTPS Sourcey endpoint. Plain HTTP is accepted only for a
loopback test server. URLs containing credentials or fragments are refused.
## Development
```bash
npm ci
npm run verify
docker build -t sourcey-mcp .
```
The verification path builds from clean output, checks all generated metadata, tests the real
HTTP-to-stdio boundary, creates an SBOM, installs the exact packed tarball into a blank project,
and repeats protocol introspection from those installed bytes.
MIT. See `SECURITY.md` and `SUPPORT.md` for reporting paths.
TDQS
Scored across 8 tools
The set splits into two clear domains (startup offers vs. Agent Readiness) with search/get/compare/inspect patterns that read as distinct actions. Within each domain the verbs are reasonably unambiguous, though the verbose, jargon-heavy descriptions for prepare_declaration, search_readiness, and search_offers create some risk of overlap confusion around eligibility vs. readiness.
All eight tools use a consistent snake_case verb_noun pattern (compare_offers, search_offers, get_readiness, get_services, etc.). Verb choices map predictably to intent (search_ for collections, get_ for a single exact record, prepare_ for submissions). No camelCase or stylistic mixing.
Eight tools is well-scoped for a read-mostly discovery/assessment server. Two coherent sub-domains (offers and readiness) are each covered with a small, focused tool set plus one meta-discovery tool, with no redundant entries.
The surface covers search, comparison, change tracking, provenance inspection, and single-record retrieval across both domains, plus service discovery and a submission-preparation path. Minor gaps remain, e.g. no dedicated get_offer for a single offer and no explicit listing of entities/subjects, though agents can work around via search.