ENDPOINT 1
https://api.ukintel.uk/mcp
MCP server metadata
- Name
- ukintel
- Version
- 1.3.0
Pay-per-call UK intelligence for AI agents, as clean JSON. Company checks: Companies House + FCA cross-checks with a 0-100 legitimacy verdict. Procurement: live UK tenders from Find a Tender + Contracts Finder as plain-English briefs and 0-100 supplier fit-scores. Grants: live GOV.UK funding calls matched to a project profile with ELIGIBLE/UNCERTAIN/INELIGIBLE verdicts, plus funder giving-history from the 360Giving open-data corpus. No signup, no API key. Paid tools charge in USDC on Base mainnet over x402: call the tool, receive a payment-required error carrying the terms, pay, and retry with the payment in _meta["x402/payment"]. An x402-aware MCP client does this for you. Start with uk_preview - it is free and returns a real, freshly-computed answer in the exact shape the paid tools return, so you can check the response before spending anything. Information, not advice.
Known tools 13
uk_previewA genuine, freshly-computed sample so an agent can see the exact response shape before spending anything.
Inferred read-onlyuk_company_profileOne UK company as clean structured JSON: status, incorporation date, company type, SIC codes, registered office, accounts and confirmation-statement due dates with overdue booleans, and officer counts.
Inferred read-onlyuk_tenders_searchLive UK public-sector tenders from Find a Tender and Contracts Finder in one call.
Inferred read-onlyuk_tender_briefOne tender as a full agent-ready dossier: parsed requirements summary, buyer, value, complete timeline with working-days-remaining, lots, document links, submission route and the official notice URL.
Inferred read-onlyuk_tenders_fit_scoreSend a supplier profile (what you do, keywords, regions, value band, certifications) and get back the best-fitting live UK tenders, each scored 0-100 by deterministic rules across five published factors - relevance, value fit, geography, timeline, buyer history - with every factor's numerator AND denominator so you can re-weight client-side, plus a what-to-emphasise note for the top matches.
Potential side effectsuk_grants_matchSend a project profile (what it is, who you are, where, how much you need) and get back the live UK grants it could actually get - ranked eligible-first with a per-criterion pass/fail table for every match, from criteria parsed once at ingest from each grant's own eligibility text.
Potential side effectsuk_grant_eligibilityOne grant, one project: a deterministic eligibility verdict with the full criteria table - each criterion quoted from the grant's own eligibility text, marked pass/fail/undeclared - plus what is missing to firm the verdict up and indicative funding.
Inferred read-onlyuk_funder_dossierWho actually funds things like yours: one UK funder's giving history aggregated from the 360Giving open-data corpus - grants made, total and typical award, size distribution, yearly pattern, most recent named awards - plus any of their grant schemes live on Find a Grant right now.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ukintel]
url = "https://api.ukintel.uk/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ukintel": {
"type": "http",
"url": "https://api.ukintel.uk/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ukintel
Remote MCP URL: https://api.ukintel.uk/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ukintel": {
"url": "https://api.ukintel.uk/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ukintel": {
"type": "http",
"url": "https://api.ukintel.uk/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ukintel",
"transport": "streamable-http",
"url": "https://api.ukintel.uk/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.