Osint Terminal
com.thetempleofdoom.osint-mcpPublished by osint-mcp.thetempleofdoom.comOfficial publisherv1.1.0Updated Oct 24, 2026
454 OSINT recon tools + server-side entity correlation & person sweeps. Keyless.
Overview
A remote MCP endpoint offering a large set of OSINT reconnaissance tools plus server-side entity correlation and person sweeps.
- What you can do
- The registry description states it provides 454 OSINT recon tools together with server-side entity correlation and person sweeps, and that it is keyless. No tool list is published in the manifest, so the exact tool names and parameters are not documented here. It is reached as a remote streamable HTTP endpoint rather than a local package.
- When to use it
- Consider it when an assistant needs open-source intelligence lookups, entity correlation, or person-focused sweeps without managing API keys. Because the tool list is not published, verify the actual capabilities against the endpoint before relying on it.
- Requirements
- A remote streamable HTTP connection to the provider's endpoint; no packages, environment variables, or headers are declared, and the description says it is keyless. Network access to the provider is required.
Installation
In SourceWeft
- Open Osint Terminal 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/com.thetempleofdoom.osint-mcp%2Fosint-terminal/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": {
"osint-terminal": {
"type": "http",
"url": "https://osint-mcp.thetempleofdoom.com/mcp"
}
}
}Tools
0Version history
2- v1.1.0LatestSep 24, 2026
- v1.0.0Sep 23, 2026
Score
56% 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
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.