FedSignal — Federal Contract Exposure, USAspending to SEC Issuer Resolution
io.sslip.244.153.73.34.insidermcpPublished by insidermcp.34.73.153.244.sslip.ioOfficial publisherv2.1.0Updated Oct 24, 2026
Federal government contracts and USAspending procurement exposure for SEC-listed companies.
Overview
Lets an assistant look up US federal contract and USAspending procurement exposure for SEC-listed companies.
- What you can do
- This remote MCP server connects federal procurement data to SEC-listed issuers, so an assistant can surface government contract exposure and USAspending award information for public companies. The registry description frames it as a way to relate federal contracts and procurement spending to SEC-registered companies. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Worth adding when an assistant needs to check how much US federal contract or procurement activity is tied to a publicly listed company, for example during research on government exposure or award momentum. Not useful for general web search or non-US procurement data.
- Requirements
- A remote streamable HTTP endpoint; no local package or runtime is needed. Authentication is declared as none, but the endpoint expects an Authorization header carrying a Bearer token. The manifest says a free API key can be obtained by posting to a keys endpoint without signup, and that paid tiers unlock additional award-momentum and contract-insider data.
Installation
In SourceWeft
- Open FedSignal — Federal Contract Exposure, USAspending to SEC Issuer Resolution in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.sslip.244.153.73.34.insidermcp%2Ffedsignal-federal-contracts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"fedsignal-federal-contract-exposure-usas": {
"type": "http",
"url": "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts"
}
}
}Tools
0Version history
1- v2.1.0LatestSep 16, 2026
Score
28% 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 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.