Skip to content
anlyon.devby Anlyon

Descovo — B2B contact data

com.descovo/descovodescovo.comstreamable-httpv1.0.0Scanned

B2B contact data for AI agents: search 700M+ people, reveal work emails. Pay per record.

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • call_operationExecute any Descovo API operation by operationId.No findings

    Why it is in this group

    • The name "call_operation" says "call": a word for a change.
    Description, as the server wrote it
    Execute any Descovo API operation by operationId. IMPORTANT: - apiKey is NOT required in the body if the MCP client sends an x-api-key header (most configs do). The backend auto-injects it. - Prefer search_endpoints() first when operation choice is ambiguous. - Use get_endpoint_details_full(operationId='...') first for complex/nested parameter shapes. Args: operationId: The operation ID to call params: Parameters dict: {"body": {...}, "path": {...}, "query": {...}} Returns: API response data or error details.
Only reads 4Show 4 read-only tools
  • get_endpoint_details_fullGet COMPLETE schema and details for a specific API operation.No findings

    Why it is in this group

    • The name "get_endpoint_details_full" says "get": a word for reading.
    Description, as the server wrote it
    Get COMPLETE schema and details for a specific API operation. Use this BEFORE calling an API to understand exactly what parameters are needed. Args: operationId: The operation ID (e.g., "syncContactEnrichment") Returns: Complete schema including all required/optional fields, request body schema, response schema, and example usage.
  • list_all_endpointsList available Descovo API endpoints with optional tag/search filtering.No findings

    Why it is in this group

    • The name "list_all_endpoints" says "list": a word for reading.
    Description, as the server wrote it
    List available Descovo API endpoints with optional tag/search filtering.
  • list_tag_packsList curated tag packs for large tool catalogs.No findings

    Why it is in this group

    • The name "list_tag_packs" says "list": a word for reading.
    Description, as the server wrote it
    List curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment).
  • search_endpointsCanonical API selection tool for endpoint discovery and ranking.No findings

    Why it is in this group

    • The name "search_endpoints" says "search": a word for reading.
    Description, as the server wrote it
    Canonical API selection tool for endpoint discovery and ranking. Use this first to get the top recommended operations for a user intent. Supports optional constraints plus tag-scoped selection via preferredTags, excludedTags, or a curated tagPack key.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Oct 29, 2026, 21:18 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.descovo.com/mcp: tools/list returned 5 tools to an anonymous client, including call_operation (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http descovo https://mcp.descovo.com/mcp --header 'x-api-key: <your-x-api-key>'
claude mcp add --transport http descovo https://mcp.descovo.com/mcp --header 'x-api-key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__descovo__search_endpoints",
      "mcp__descovo__list_tag_packs",
      "mcp__descovo__list_all_endpoints",
      "mcp__descovo__get_endpoint_details_full"
    ],
    "ask": [
      "mcp__descovo__call_operation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as descovo. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/com.descovo/descovo/verify?hash=adc67b3be60495a2f15c81d48b7585b8aaa86aa313c9a7b05e835227e5e85cfd" | jq -e '.changed == false'

Pinned hash adc67b3be604, from Oct 29, 2026, 21:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.descovo/descovo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for com.descovo/descovo
[![anlyon.dev](https://anlyon.dev/badge/com.descovo/descovo.svg)](https://anlyon.dev/servers/com.descovo/descovo)

Source: MCP Registry. Synced Oct 29, 2026, 21:17 UTC.