verifind-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_API_KEY | Yes | API key for the OpenAI-compatible LLM endpoint (defaults to Groq) | |
| TAVILY_API_KEY | Yes | API key for Tavily search |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verified_searchA | Finds real things matching a query — products, opportunities, tickets, jobs, events, whatever — by running a real web search and having a model restructure ONLY what that search actually returned into the JSON shape you specify. Every item's source field is checked in code against the literal URLs the search returned, so a result can't be invented or hallucinated: if the model can't back a claim with a real fetched page, that item is dropped rather than guessed at. Give it a plain-language query and a JSON Schema for one result item (sourceField, default "sourceUrl", is added automatically if you don't include it). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clear from its name and detailed description.
A single tool means there is no inconsistent naming convention to worry about. verified_search is clear, readable snake_case and matches the server's purpose.
One tool feels thin, especially since the description claims coverage of many domains like products, jobs, events, and tickets. However, the tool is flexible enough that a single entry point may be reasonable for a narrowly focused server.
The tool covers the core need of verified search with hallucination control and customizable result schemas. It lacks obvious pagination or refinement options, but those are not major dead ends for the stated purpose.