
AnswerPool (formerly CortexAssay)
io.github.blakeyoungerPublished by GitHub account blakeyoungerv1.0.2Updated Oct 25, 2026
Renamed to AnswerPool; see io.github.blakeyounger/answerpool. SEC, Federal Register, funding
Overview
AnswerPool (formerly CortexAssay) is a remote MCP endpoint that gives an assistant access to SEC, Federal Register and funding data.
- What you can do
- Connect an assistant to a hosted endpoint covering SEC filings, Federal Register documents and funding information. Free discovery tools are said to work without a key, while a bearer credit key unlocks the rest. The manifest lists no individual tools, so the exact operations are not documented here. The server has been renamed to AnswerPool, and this entry points to the newer identifier.
- When to use it
- Useful when an assistant needs regulatory filings, Federal Register notices or funding data and you prefer a hosted endpoint over a local package. Check the renamed AnswerPool entry first, since this identifier is the older one.
- Requirements
- A remote streamable HTTP endpoint; nothing to install locally. An Authorization header carrying a bearer credit key is needed for the paid tools, while free discovery tools reportedly work without it. Network access to the hosted service is required.
Installation
In SourceWeft
- Open AnswerPool (formerly CortexAssay) 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.github.blakeyounger%2Fcortexassay/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": {
"answerpool-formerly-cortexassay": {
"type": "http",
"url": "https://cortexassay.com/mcp"
}
}
}Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
67% 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
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- 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.