MCP Verify
Trust, freshness, policy, and discovery layer for public MCP servers.
Should I use this
Quality & Safety
A
Findings (1)
- LOWin recommend_servers
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~2,537Tokens (tool definitions)
~894 BTypical response size
Moderate attention impact (1.98% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"verify": {
"url": "https://verify.sentinelsignal.io/mcp"
}
}
}Remote endpoints
https://verify.sentinelsignal.io/mcpstreamable-httpWhat it can do
Tool inventory
No publishable tool enumeration has been recorded.
Recommended Prompts
search_research
Search for information about [topic] using MCP Verify
Expected tools:
searchfind_specific
Find [specific item] using MCP Verify
Expected tools:
searchretrieve_data
Get details about [item] from MCP Verify
Expected tools:
fetchfetch_info
Fetch [information type] using MCP Verify
Expected tools:
fetchlist_items
List all [items] available in MCP Verify
Expected tools:
list_agentsCommunity
Evidence
Recent observations
failed observationversion not recorded—
failed observationversion not recorded—
verifiedversion not recorded22 tools
verifiedversion not recorded22 tools
verifiedversion not recorded22 tools