revnuvo-company-intelligence
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVNUVO_API_KEY | Yes | Your Revnuvo API key. Obtain a free key at https://app.revnuvo.site (100 calls/month, no credit card required). Used to authenticate to the Revnuvo MCP server. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| revnuvo_search_companyA | Search known companies by keyword (name or domain fragment). Returns matched domains with observation recency. |
| revnuvo_get_companyA | Company summary for a domain: what we observe, since when, how fresh. Use to decide whether deeper calls are worth it. |
| revnuvo_get_company_stateA | Latest observed state of a domain (technologies, fingerprint freshness, observation hash) for 'as of now' questions. |
| revnuvo_get_company_timelineC | Chronological change timeline for a domain. Free plan sees the last 7 days. |
| revnuvo_get_company_technologiesA | Detected technologies for a domain, each with detection evidence and confidence. Answer 'what does X run on?'. |
| revnuvo_get_company_changesB | Recent technology/infra changes for a domain with before/after and evidence. Answer 'what changed at X?'. |
| revnuvo_search_signalsA | Cross-company buying/intent signals (e.g. vendor swaps, new tooling) ranked by score, with evidence. Free plan: last 7 days. |
| revnuvo_monitor_companyA | Watch a domain for changes; a baseline scan is captured immediately and rechecks run on schedule. Requires a webhooks-capable plan for delivery. |
| revnuvo_verify_companyA | On-demand verification pass of a domain (live HTTP + DNS evidence). Use to confirm a signal before acting on 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 9 tools
Most tools have distinct intents: search, summarize, inspect technologies, review changes, verify, monitor, and find signals. Some overlap exists between get_company_state, get_company_timeline, and get_company_changes, which all describe observed domain data in slightly different ways.
Naming is mostly consistent with the revnuvo_ prefix and verb_noun pattern, such as get_company_* and search_company. The main deviation is search_signals, which does not follow the company-object naming used elsewhere, and the varying granularity of get_company_state vs get_company_changes.
Nine tools is well within the ideal range for a focused company-intelligence server. Each tool maps to a distinct workflow—discovery, summary, deep-dive, changes, signals, verification, and monitoring—so the count feels intentional rather than padded.
The core lifecycle is well covered: search companies, get summaries, inspect state/technologies/changes/timeline, find signals, verify, and monitor. The main gap is that monitor_company starts a watch but there is no tool to list, update, or stop existing monitors, which is a minor dead end.