
Sourcey
io.github.sourceyPublished by GitHub account sourceyv1.0.1Updated Nov 3, 2026
Stdio bridge to Sourcey startup offers and Agent Readiness report cards.
The publisher's own server: Sourcey
Overview
Local stdio bridge that relays an assistant's tool calls to Sourcey's hosted MCP server for startup offers and Agent Readiness report cards.
- What you can do
- Search and compare startup credits, discounts, free tiers, programs and deals
- Inspect evidence, freshness, eligibility unknowns and the signed change feed for offers
- Search and inspect Agent Readiness report cards, including grades, findings, blockers and coverage
- Prepare canonical Agent Readiness declaration YAML without assigning a grade
- Discover Sourcey's paid HTTP services and x402 endpoint without paying inside MCP
- When to use it
- Use it when your MCP client needs a local command instead of a remote endpoint and you want an assistant to research startup offers or Agent Readiness reports with cited evidence. Clients that support remote MCP can connect to the hosted server directly instead.
- Requirements
- Runs as a local process via npx from the npm package @sourcey/mcp-server, so Node.js is needed. Network access to the hosted Sourcey HTTPS endpoint is required; the optional SOURCEY_MCP_URL variable can point at another HTTPS Sourcey endpoint. No credentials are declared.
Installation
In SourceWeft
- Open Sourcey in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Sourcey
[Sourcey mark]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:
Gemini CLI can install the hosted connection and bundled sourcey-research skill directly from this repository:
--ref main installs the current extension from the repository. Without it, Gemini CLI selects the older v1.0.0 release archive, which predates the extension manifest. The extension uses the remote Sourcey data MCP; it does not start the npm stdio bridge or invoke Sourcey's separate documentation generator.
Use that URL directly when your client supports remote MCP. This package is the thin stdio bridge for clients that require a local command:
The bridge downloads no offer dataset 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 data or tool-description update therefore needs no package release.
Agent plugins
This repository also packages the hosted Sourcey connection for Claude, Cursor, Grok Build and portable ChatGPT/Codex distribution. Host manifests are in .claude-plugin/, .cursor-plugin/ and .grok-plugin/; root plugin.json carries Agent Plugins metadata for ChatGPT/Codex. Portable mcp.json and host-specific .mcp.json point directly to https://mcp.sourcey.com/mcp. The bundled Sourcey research skill shows how to check evidence and eligibility before recommending an offer. Marketplace review and live cards are separate from the source package; no ChatGPT/Codex approval is claimed here.
The Claude directory uses the scoped plugin folder at plugins/sourcey. It contains only the hosted connection, research skill, mark, license and README. npm run generate:metadata copies its shared files from the existing root sources; npm run check:metadata verifies the exact file set and bytes. The optional stdio bridge, its dependencies and repository ownership proofs stay outside that installable folder. Other clients can continue using the root manifests.
The plugin connects to Sourcey's startup-offer and Agent Readiness data. It does not run Sourcey's separate documentation generator or pay for Sourcey's HTTP services. The current square mark is in assets/sourcey-mark.png; privacy, terms and support are available on the product site.
Try these prompts after installing the plugin:
- “Find current cloud-hosting startup offers in Sourcey. Show the original source, last-checked date, and any eligibility unknowns for three results.”
- “Compare two of those offers using their recorded terms and evidence. Separate confirmed conditions from anything Sourcey has not verified.”
- “Find a Sourcey Agent Readiness report card and explain the tested workflows, blockers, and claims that remain unverified.”
The Claude plugin's .mcp.json declares only the public HTTPS Sourcey MCP server. It does not run this repository's optional npm stdio bridge or read a local credential. Search terms and record references deliberately sent to the hosted MCP are handled under Sourcey's privacy policy; request bodies are not persisted as product records.
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, its OpenAPI contract is at
api.sourcey.com/openapi.yml, and x402 discovery is at
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
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.
Source: README.md at commit 47c45df
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts