Seneca Research Platform
com.professionalaiagentsPublished by professionalaiagents.comOfficial publisherv1.0.2Updated Oct 24, 2026
One prompt. ~100 independent AI models. One report: consensus, disagreements, and minority insights.
Overview
Lets an assistant query a remote research platform that runs one prompt across roughly 100 AI models and returns a single report.
- What you can do
- Seneca Research Platform is a remote MCP endpoint that takes a single prompt and fans it out to about 100 independent AI models. It then returns one consolidated report covering consensus, disagreements, and minority insights. The manifest lists no individual tools, so the exact call surface is not documented here.
- When to use it
- Worth adding when you want a multi-model second opinion on a question rather than a single model's answer, for example to surface disagreement or minority views. Less useful for routine single-model tasks or anything needing documented, granular tool control.
- Requirements
- A remote streamable HTTP endpoint; no local package or runtime is declared. Authentication is required: a bearer token sent in the Authorization header, described as a Seneca workspace API key. Keys are created and revoked through the provider's developer page. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Seneca Research Platform in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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/com.professionalaiagents%2Fseneca/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": {
"seneca-research-platform": {
"type": "http",
"url": "https://mcp.seneca.professionalaiagents.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.2LatestOct 14, 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 listed15 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.