_ registry / mcp streamable-http · checked 34m ago

revnuvo-company-intelligence

https://mcp.revnuvo.site

Registry code: e97599107e894fbe

api record

Revnuvo observes company websites, technologies, DNS and infrastructure over time, detects meaningful changes, and returns evidence-backed intelligence. Start with revnuvo_search_company or revnuvo_get_company for a domain, revnuvo_search_signals to find which companies recently changed, and revnuvo_monitor_company to watch a domain for future changes. Every response is timestamped, confidence-aware and carries detection evidence. Revnuvo reports what was measured — never purchase intent.

How to read confidence (0-1): 0.95 = direct header evidence (e.g. 'server' or 'x-powered-by' response…

endpoint
https://mcp.revnuvo.site/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is revnuvo-company-intelligence live?
Yes — it answered the hub's last check (checked 34m ago). It answered 100% of checks over the last 30 days.
Is revnuvo-company-intelligence free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does revnuvo-company-intelligence have?
9 tools: revnuvo_get_company, revnuvo_get_company_timeline, revnuvo_get_company_changes, revnuvo_search_signals, revnuvo_monitor_company, revnuvo_get_company_state, revnuvo_verify_company, revnuvo_search_company, ….
Is revnuvo-company-intelligence safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.1%· all time 99.4%

latency
102ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 566 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business crm & sales
used for
  • look up a company's technology stack
  • track changes on a company website
  • monitor a company domain
  • search companies with recent changes
takes → gives
text → data
tools
8 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 auth-required 9 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • revnuvo_get_company reads auth-required 18h ago

    Retrieve an overview of a company domain from Revnuvo's observation history: current technologies (with confidence), DNS records, first/last observation timestamps, total observation count and the hash of the latest observed state. Use it to answer 'what do we know about this company?'. Returns not_observed (404-equivalent) when Revnuvo has no history yet.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Company domain, e.g. 'hubspot.com'."
    }
  }
}
    arguments 12 lines
  • revnuvo_get_company_timeline reads auth-required 18h ago

    Retrieve the chronological observation history for a company: each observation's timestamp, source, confidence and state hash, plus every detected change event with before/after values. Use it to answer 'how did this company's stack evolve?'. History depth depends on your plan (free: 7 days).

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1,
      "description": "Max entries per list (default 50)."
    },
    "domain": {
      "type": "string",
      "description": "Company domain."
    }
  }
}
    arguments 19 lines
  • revnuvo_get_company_changes reads auth-required 18h ago

    Retrieve observed changes at a company domain: technology added/removed/changed, DNS/MX and nameserver changes, and website-state changes — each with before/after values, detection timestamp, confidence and evidence. Answers 'what changed at this company and when?'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1,
      "description": "Max changes returned."
    },
    "since": {
      "type": "string",
      "description": "ISO-8601 timestamp; return changes detected after this time. Defaults to your plan's history window."
    },
    "domain": {
      "type": "string",
      "description": "Company domain."
    }
  }
}
    arguments 23 lines
  • revnuvo_search_signals reads auth-required never probed

    Search Revnuvo's signal feed across all observed companies. Filter by domain, technology (e.g. 'vue', 'hubspot'), event type (technology_added, technology_removed, technology_changed, mx_changed, nameserver_changed, website_changed) and minimum signal score (1-100). Answers 'which companies recently adopted technology X?' — every signal includes before/after state, evidence and confidence. Signals are observed changes, not purchase-intent claims.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1,
      "description": "Max signals returned."
    },
    "since": {
      "type": "string",
      "description": "ISO-8601 timestamp lower bound."
    },
    "domain": {
      "type": "string",
      "description": "Restrict to one company domain."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Pagination offset."
    },
    "min_score": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Minimum signal score (1-100)."
    },
    "event_type": {
      "enum": [
        "technology_added",
        "technology_removed",
        "technology_changed",
        "mx_changed",
        "nameserver_changed",
        "website_changed"
      ],
      "type": "string",
      "description": "Change type filter."
    },
    "technology": {
      "type": "string",
      "description": "Technology name filter, e.g. 'nextjs'."
    }
  }
}
    arguments 48 lines
  • revnuvo_monitor_company changes data auth-required never probed

    Start monitoring a company domain: Revnuvo scans it on your chosen interval (24h on the free plan, 6h on paid plans), records every observation, detects changes, and you retrieve new signals via revnuvo_search_signals or receive webhook/email deliveries configured in your Revnuvo dashboard. Use it to answer 'alert me when something changes at this company'. Counted against your plan's domain limit.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Company domain to monitor."
    },
    "interval_hours": {
      "enum": [
        6,
        24
      ],
      "type": "integer",
      "default": 24,
      "description": "Scan interval in hours (24 = free plan; 6 requires Developer plan or above)."
    }
  }
}
    arguments 21 lines
  • revnuvo_get_company_state reads auth-required 34m ago

    Retrieve the company's latest full observed state: HTTP status and server headers, detected technologies with per-technology evidence and confidence, detected scripts, and DNS (NS/MX/A) records. This is a point-in-time measurement, timestamped and hashed. Use it when you need the complete current picture rather than a summary.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Company domain, e.g. 'vercel.com'."
    }
  }
}
    arguments 12 lines
  • revnuvo_verify_company reads auth-required never probed

    Verify what Revnuvo can substantiate about a company domain: whether it has observation history, how many observations, the latest observed state hash, and (when the Trust service is reachable) an independent infrastructure trust score. Use it for diligence flows that need evidence-backed company verification rather than assumptions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Company domain."
    }
  }
}
    arguments 12 lines
  • revnuvo_search_company reads auth-required 34m ago

    Search companies previously observed by Revnuvo. Returns the domain, when it was first seen, how many observations exist, its most recently detected technology stack, and the last scan time. Use this to check whether Revnuvo already has history for a company before querying deeper. Only observed companies are returned — nothing is invented.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1,
      "description": "Max results (default 50)."
    },
    "query": {
      "type": "string",
      "description": "Full or partial domain, e.g. 'stripe' matches 'stripe.com'. Empty = list recent."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Pagination offset."
    }
  }
}
    arguments 22 lines
  • revnuvo_get_company_technologies reads auth-required 34m ago

    Retrieve the technologies currently detected at a company domain — each with name, category, version when detectable, confidence (0-1), and the evidence string that produced the detection (e.g. a header value or a script URL). Answers 'what technologies does this company use?'. Absence of a technology means not-detected, never proven-absent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Company domain."
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e97599107e894fbe.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e97599107e894fbe/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e97599107e894fbe/badge.svg)](https://brick.blue/agent/e97599107e894fbe?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.