SponsorFinder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port for the Node entry (src/entry/node.ts). Ignored by stdio and Cloudflare Workers. | 3001 |
| UPSTREAM_TIMEOUT_MS | No | Upstream request timeout in milliseconds. | 10000 |
| SPONSORFINDER_API_KEY | Yes | Upstream x-api-key header value. Server-side secret — never exposed to MCP clients. | |
| SPONSORFINDER_API_BASE | Yes | Base URL of the upstream SponsorFinder API, no trailing slash (e.g. https://api.sponsorfinder.io). |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_sponsor_licenseA | Check whether a company holds a UK or Netherlands work-visa sponsorship licence. Handles typos and partial names. Returns licence routes, ratings, locations and register dates. For exploring or filtering many companies, use search_sponsors instead. |
| search_sponsorsA | Exploratory list search of the sponsor register with optional filters (city/route for UK, sponsor type for NL). Returns a compact list with a total count. For checking one specific company, prefer check_sponsor_license. |
| get_sponsor_detailsA | Full record for one organization by id: routes, ratings, locations and register dates (UK), or sponsor type and KvK number (NL). Optionally include register change history. |
| get_register_infoA | Register statistics, data freshness, and terminology for the UK and Netherlands sponsor registers. Use this to explain what a licence, route, rating, or sponsor type means. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: checking by name (check_sponsor_license), searching with filters (search_sponsors), getting full details by ID (get_sponsor_details), and retrieving register metadata (get_register_info). The descriptions explicitly differentiate them.
All tool names follow a consistent verb_noun pattern (check_, get_, search_) using snake_case. The verbs and objects are semantically appropriate and uniform.
Four tools cover the core functionalities for a sponsor license lookup server without being excessive or insufficient. The scope is well-defined.
The tool set provides complete coverage for a read-only sponsor information service: name-based lookup, ID-based details, filtered search, and register metadata. No obvious gaps are present.