Skip to main content
Glama
Sourcey

Sourcey

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SOURCEY_MCP_URLNoSelect another HTTPS Sourcey endpoint. Plain HTTP is accepted only for a loopback test server. URLs containing credentials or fragments are refused.https://mcp.sourcey.com/mcp

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_offersA

Search current startup credits and deals, including cloud credits, SaaS discounts, free tiers, grants, perks, and partner offers. Filter by query, vendor, or category and evaluate eligibility from typed company facts; unknowns remain explicit.

compare_offersA

Compare two to ten startup credit or deal offers side by side, including value, access requirements, eligibility, freshness, and evidence. Unknown eligibility and unsupported stacking remain explicit.

inspect_evidenceA

Inspect the provenance behind startup credits and deals. Resolve one to ten exact revisions to supporting events and observations, including freshness and dispute status.

get_changesA

Track added, changed, withdrawn, and removed startup credits, discounts, free tiers, perks, and deals through Sourcey's signed change feed after an optional cursor.

search_readinessA

Search published Agent Readiness report cards. Each card grades one named job on a vendor's service by where a person or the vendor has to step in on an agent's path to it, from its listing and from probes that send the job's request with no account (or, where its interface has no public endpoint, read the vendor's OpenAPI document for it): one letter, A+ to F, over Discover, Authority, Onboard, Pay, Confirm and Sustain, and how often a person is needed; whether the job itself is reachable (not yet run), verified by a run (proof only, which never changes a step or the letter), or has no machine interface; the evidence label; freshness; and the canonical report URL. Service readiness is separate from startup-credit eligibility.

get_readinessB

Get one published Agent Readiness report card: the job and the interface whose path it grades (none for an F card whose listing names no interface), the letter and its statement, each step's outcome, approvals and human workarounds, the evidence label (probed, or the job verified by a run), discovery facts from the service's own descriptors and llms.txt, the declared surface, policy identity, provenance, and canonical URL. Resolve by immutable profile ID or by one Entity plus exact product and job.

prepare_declarationA

Prepare the canonical Agent Readiness declaration for one service and job: participants, endpoints, API and MCP interfaces, the job operation on each interface that performs the job (the request the probes send with no account, or the operation in the vendor's OpenAPI document where the interface has no public endpoint), and optional job bindings for a verified run. The company must already exist in Sourcey and resolves by exact identity; an unknown company returns identity_allocation_required. Complete declarations use POST /v1/submissions as product agent_readiness. Drafts grant no publication, verification or grade, and startup credits and deals never count as service readiness.

get_servicesA

Discover Sourcey's enabled paid agent services and canonical HTTP resources, including exact request and response contracts, price floor, policy links, and x402 discovery. Payment and durable job status remain on the product HTTP API; this read-only MCP tool never signs, settles, or interprets a payment.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct action and resource: search/compare offers, inspect evidence, track changes, search/get readiness, prepare a declaration, and discover services. The offer and readiness tools are clearly separated, and search vs. get/compare boundaries are explicit.

Naming Consistency5/5

All eight tools follow a consistent snake_case verb_noun pattern: compare_offers, search_offers, inspect_evidence, get_changes, search_readiness, get_readiness, prepare_declaration, get_services. There are no mixed styles or vague standalone verbs.

Tool Count5/5

Eight tools is well scoped for a server covering startup offers/credits plus Agent Readiness reports. Each tool has a clear role, and the set avoids both thinness and unnecessary sprawl.

Completeness4/5

The offer side covers discovery, comparison, provenance, and change tracking; readiness covers search, detail, and declaration preparation. Minor gaps remain, such as no direct single-offer retrieval tool and no MCP tool for submitting or publishing a prepared declaration, though the latter is explicitly delegated to the product HTTP API.

Maintenance

ActivityMaintained
ResponsivenessLimited data