
Scout Intel MCP — The Google for AI Agents
io.github.omniologynow-rgbPublished by GitHub account omniologynow-rgbv1.0.3Updated Oct 24, 2026
The Google for AI agents — company intel, competitor tracking, market research via MCP. JSON output
Overview
A remote or local MCP server that gives an assistant company intelligence, competitor tracking and market research, returning JSON output.
- What you can do
- Look up company intelligence on businesses the assistant is asked about, per the description's positioning as a search layer for AI agents. Track competitors and gather market research through the same interface. Return results as JSON for downstream use. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Useful when an assistant needs quick company, competitor or market context during research or sales-style tasks, and a hosted search-style service is acceptable. Less suitable if you need documented per-tool control or offline operation.
- Requirements
- Runs as a remote streamable HTTP endpoint or as a local PyPI package over stdio. OAuth authentication is required. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Scout Intel MCP — The Google for AI Agents in the dashboard and add it to a workspace.
- Connect the required 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/io.github.omniologynow-rgb%2Fscout-intel-mcp/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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"scout-intel-the-google-for-ai-agents": {
"type": "http",
"url": "https://scout-intel.mcpize.run/"
}
}
}Tools
0Version history
1- v1.0.3LatestSep 16, 2026
Score
60% 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.
- License10 pts
Declare a license in the repository or the registry entry.