All servers / Security / ChainPatrol MCP server
ChainPatrol MCP server
The official ChainPatrol MCP server — every public API capability as an MCP tool
Tested by ConnectATDScore 79 out of 100. Tested 2026-11-19 on package version 1.19.2. Package: @chainpatrol/mcp
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 17 / 20 | |
| Package safety | 16 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.6 seconds including download)
- Tools offered: 82
- Last published: 2026-11-16
- Weekly downloads (npm): 624
- License: UNLICENSED · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
asset_changelog6 of 6 parameters describedAsset changelog. Assets can be changed for various reasons, such as false positives, false negatives or normal reviews.
asset_check1 of 1 parameter describedAnswers 'is this asset known to be malicious?'. Takes one piece of content — a URL, domain, social handle, app listing, or wallet address — and returns its status (`BLOCKED`, `ALLOWED`, or `UNKNOWN`), the source that decided it, the reason, and the per-source breakdown. Use it when you have a specific asset in hand. To search the blocklist by pattern instead, use `/asset/search`; to find whether a report already exists for an asset, use `/reports/search`.
asset_connections4 of 4 parameters describedAnswers 'what led to this asset, and where does it lead?'. Takes one asset (by `assetId` or `content`) and returns the assets linked into it (`upstream`: the page that ran the ad, the ad that linked to it, the account that claimed it) and out of it (`downstream`: what it redirects to, links to or claims), followed `depth` hops on each side, as two graphs of assets and typed links. Nodes carry the same id, type, content and status that `/asset/search` returns. Available to organizations the threat graph connections rollout has been turned on for; others receive `FORBIDDEN`.
asset_details1 of 1 parameter describedDeprecated — prefer `/asset/check`, which returns the same status plus the deciding source and per-source breakdown. Answers 'what is this asset's status, and which report set it?'. Returns the status, the reason (`report` for a ChainPatrol report, `eth-phishing-detect` for that list), and the id and link of the report behind the latest status change.
asset_follow3 of 3 parameters describedEmail the person behind these credentials when the asset's status changes and when its takedown completes. Name the asset by `content` or `assetId`. Needs a user-scoped API key or a signed-in session — organization API keys are refused. Following twice is not an error; up to 100 assets per person per organization.
asset_follows_list1 of 1 parameter describedEvery asset the person behind these credentials follows in this organization, newest first, with its current status and this organization's takedown. Poll it to see status changes without email. Needs a user-scoped API key or a signed-in session.
asset_list6 of 6 parameters describedAnswers 'which assets does ChainPatrol hold at this status?'. Returns a paginated list defaulting to `BLOCKED`, optionally narrowed to a single `type` and to a date range. Omit `type` to sweep every asset type on one cursor, which is the cheapest way to mirror the whole blocklist. Built for bulk export and sync — pass `next_page` from the previous response to continue. To check one specific asset, use `/asset/check` instead; for an organization's own monitored assets, use `/organization/assets`.
asset_parse1 of 1 parameter describedParse and normalize asset content to extract structured information
asset_scan_live4 of 4 parameters describedInitiate an asset scan. Optionally provide an organization slug for brand impersonation detection and a callback URL to receive results when the scan completes.
asset_search4 of 4 parameters describedSearch for an asset by content or ID and get its status, associated reports, and takedown details
asset_submit2 of 2 parameters describedSubmit a list of assets such as domains, social profiles, or blockchain addresses. Automation will classify and assign them to appropriate organization(s).
asset_unblock0 of 2 parameters describedUnblock an asset if it belongs to your organization, or create a dispute if it doesn't. Requires API key.
asset_unfollow3 of 3 parameters describedStop the status emails for an asset. Name it by `content` or `assetId`. Never refused for capacity, and unfollowing an asset you do not follow is not an error.
dark_web_credentials_search4 of 4 parameters describedSearch DarkOwl for leaked credentials tied to an allowlisted brand target. Passwords are returned in plaintext when available. Treat the response as sensitive, use TLS, and never log response bodies.
dark_web_credentials_targets2 of 2 parameters describedList the domains, email addresses, and crypto addresses that can be searched for a brand.
detection_configs_create8 of 8 parameters describedCreate a config that makes a detection source run for an organization. Sources that are disabled by default have no config, so they cannot be enabled through /detection/configs/update until one is created. A source can have several configs, each with its own query, schedule or brand.
detection_configs_delete2 of 2 parameters describedDelete one detection config so it stops scanning. Other configs sharing the same source keep running. Deleting the last config for a source that is enabled by default is not permanent, since automation re-creates it; disable it through /detection/configs/update instead.
detection_configs_list1 of 1 parameter describedList all threat detection sources for an organization. Each source includes its individual configurations with details like schedule, status, and source-specific settings.
detection_configs_run0 of 4 parameters describedRun one or many organization detection configs and return run status per config.
detection_configs_update1 of 9 parameters describedUpdate an organization threat detection config status, schedule, and config fields.
detection_configs_validate0 of 6 parameters describedValidate detection configs by checking recent detection results, optionally running each config first.
detection_drift0 of 8 parameters describedAnalyze organization detection configs and surface zero-result, noisy-source, and stale-query drift signals.
detection_list10 of 10 parameters describedList suspected threats for an organization using API key authentication, newest first. A suspected threat is an unconfirmed result of automated threat detection; use the `blockStatus` filter to find the ones confirmed as threats. Returns human-readable confidence levels (none, low, medium, high) and report status. Supports filtering by source, confidence level, raw score range, asset status, asset type and creation time, plus search. Pages hold up to 1000 results: pass `nextCursor` back as `cursor` until it is absent, set `includeTotal` to get the number of matching suspected threats without paging, and use `startDate` to fetch only suspected threats created since your last sync.
detection_sources_list1 of 1 parameter describedList the catalog of threat detection sources ChainPatrol can run, including the scopes each source supports and the JSON Schema its config object must satisfy. Sources that do not apply to the organization's industry are omitted.
dispute_create0 of 3 parameters describedCreate a new dispute for an asset via the external API. Requires API key.
get_organization_reports2 of 27 parameters describedGet reports for an organization based on organization slug and filters
get_public_organization_metrics2 of 4 parameters describedGet public metrics for one or more organizations
healthchecks_assets_dead_asset_spike0 of 6 parameters describedCompares the count of `DETECTED_AS_DEAD` LivenessStatusEvent rows in the current window against the baseline rate from the prior `baselineDays`. Severity fires only when the current count clears `minSpikeCount` (suppresses noise when the org has near-zero baseline activity) and exceeds the configured multiplier. Useful for catching liveness-checker regressions after platform changes (captcha rollouts, anti-bot updates) which falsely mark live assets as dead.
healthchecks_detections_silent_configs0 of 6 parameters describedValidates that each enabled detection config has produced at least the configured minimum number of results within the lookback window. Returns the uniform healthcheck result shape.
healthchecks_listno parametersReturn the registry of healthchecks ChainPatrol exposes today, including planned checks that are not yet implemented on the backend. Clients should iterate this list and only call endpoints where `implemented` is true.
healthchecks_missing_contact_url0 of 1 parameter describedFlags organizations that have no contactUrl configured. The contact URL is the main communication channel (typically Slack or Telegram) used to reach the customer.
healthchecks_reviewing_backlog0 of 3 parameters describedCounts proposals in PENDING review state for the org and grades severity (ok/warn/fail) against the configurable thresholds.
healthchecks_reviewing_old_proposals0 of 3 parameters describedCounts PENDING proposals older than the warn / fail age thresholds (default 7 / 14 days) and lists the oldest offenders.
healthchecks_takedowns_automation_off0 of 3 parameters describedFlags orgs where takedown service is enabled but `isAutomatedTakedownsActive` has been off for longer than the configured age threshold (default warn 30 days, fail 60 days). Age is derived from the most recent SERVICES_AUTOMATED_TAKEDOWNS_UPDATED entry in OrganizationEvent, falling back to Organization.updatedAt. Orgs without takedown service enabled at all are excluded.
healthchecks_takedowns_cancelled_count0 of 4 parameters describedCounts transitions into the CANCELLED status from the TakedownEvent log within the configured lookback window. Cancellations should be rare (typically 0-2 per week); a higher count usually signals a quality problem in the proposal funnel or a misuse of the CANCELLED status.
healthchecks_takedowns_in_progress_volume0 of 3 parameters describedCounts takedowns currently IN_PROGRESS for the org regardless of age. Complements `takedowns.stale-in-progress` (which only flags items past a staleness threshold) — a high overall pile-up signals submission-format or vendor-side issues even when individual items are not yet stale.
healthchecks_takedowns_stale_in_progress0 of 4 parameters describedCounts takedowns that have sat in IN_PROGRESS past the staleness threshold (default 7 days) and lists the oldest offenders.
healthchecks_takedowns_todo_volume0 of 3 parameters describedCounts takedowns sitting in TODO status for the org. A backlog typically signals either an automation gap on a new threat surface, or manual-filing capacity issues on the takedown team.
metrics_breakdown2 of 5 parameters describedGet blocked threat counts grouped by day, asset type, or brand.
metrics_false_positive_rate6 of 6 parameters describedGet the share of blocks that were later reversed for a date range, for one organization (`slug`) or several (`slugs`). Returns a pooled `total`, a `byOrganization` breakdown, and a `byAssetType` breakdown. Every asset type blocked in the range is returned, including ones with no false positives. The range bounds when the asset was blocked; whether the block still stands is read as of now, so a recent range reads low simply because its reversals have not happened yet.
metrics_found2 of 4 parameters describedReturn the default 'found' metric for an organization, defined as customer-facing new threats.
metrics_found_by_source4 of 4 parameters describedCount distinct currently blocked assets whose earliest report for the organization falls in the date range, split into customer vs ChainPatrol (staff + automation). Blocked is current status or pending BLOCKED, not blockedAt. This does not equal /metrics/found.
metrics_summary2 of 4 parameters describedGet customer-facing organization metrics and blocked threat breakdowns for a date range.
metrics_takedown_success_rate7 of 7 parameters describedGet the share of takedowns that ended in a removal, broken down by asset type, for a date range. The range bounds when a takedown was first submitted to a provider, so takedowns opened but never filed are excluded; outcomes are read as of now, and takedowns still being worked count against the rate.
metrics_takedown_time9 of 9 parameters describedGet the median time from takedown start to completion, broken down by asset type, for a date range. Crypto address (ADDRESS) takedowns are left out unless you filter to them: an address is reported on many sites at once and how long its takedown takes depends on how many platforms you want covered. `excludedAssetTypes` in the response lists what was left out.
metrics_takedown_time_by_provider8 of 8 parameters describedGet the median time from takedown start to completion, broken down by the provider a takedown was filed against, for a date range. Each takedown is counted once per provider role it carries (hosting provider, domain registrar, TLD registrar). Crypto address (ADDRESS) takedowns are left out, as in the other time-to-takedown metrics; `excludedAssetTypes` in the response lists them.
metrics_takedown_time_trend7 of 7 parameters describedGet the median time from takedown start to completion bucketed by the month a takedown completed, over a trailing window of whole months, together with the month-over-month change. Returns one series per requested asset type, or a single pooled series. Crypto address (ADDRESS) takedowns are left out unless you filter to them: an address is reported on many sites at once and how long its takedown takes depends on how many platforms you want covered. `excludedAssetTypes` in the response lists what was left out.
metrics_time_to_detection5 of 5 parameters describedHow long threats were already live before the earliest automated detection of the asset, for any organization. Broken down by asset type, for distinct assets this organization blocked in the date range that are still blocked today. The clock runs from when the asset was first seen live to its earliest automated detection; a human report does not stop it. Each median is a minimum.
operations_queues_snapshot0 of 3 parameters describedReturn pending review and takedown queue state with SLA and age buckets for operational monitoring.
organization_asset_groups_create1 of 1 parameter describedCreate a new asset group for organizing your organization's assets.
organization_asset_groups_delete1 of 1 parameter describedDelete an asset group. Assets in this group will become ungrouped.
organization_asset_groups_listno parametersList all asset groups belonging to your organization with asset counts.
organization_asset_groups_update2 of 2 parameters describedRename an existing asset group.
organization_assets_add2 of 2 parameters describedBatch add multiple assets to your organization's allowlist. Each asset is automatically parsed and classified. Assets are normally approved as ALLOWED; an asset ChainPatrol currently has BLOCKED, and requests from integration organizations, go to manual review instead. Supports optional group assignment and an optional allowlist expiry, for the whole request or per asset.
organization_assets_delete1 of 1 parameter describedRemove an asset from your organization's allowlist. This performs a soft delete.
organization_assets_list6 of 6 parameters describedList all assets belonging to your organization with optional filtering by type, group, and search query. Supports pagination.
organization_assets_set_expiry3 of 3 parameters describedSet, renew or clear when assets drop off your organization's allowlist. After the expiry passes, assets stay for a 14-day grace period, then are removed from your organization; their status does not change. Requires an organization API key with write access, or an organization owner or admin.
organization_assets_update4 of 4 parameters describedUpdate an asset's name, description, or group assignment. The asset must belong to your organization.
organization_brands_list1 of 1 parameter describedList every brand belonging to an organization. Pass `slug` to choose the organization when your credentials can reach more than one (user-scoped API keys, staff and member sessions); organization-scoped API keys can omit it and get their own organization. Returns parent brands (`type: ORGANIZATION`), individual / employee brands (`type: INDIVIDUAL`), and product brands (`type: PRODUCT`) in one call, including configuration fields: `brandColors` (HEX strings), `includedTerms`, `excludedTerms`, `tickers`, `avatarUrl`, `websiteUrl`, and `twitterHandle`. Each brand also reports `useOrganizationDocs` (when true, the brand inherits its LOA from the org), a `legalDocuments` block with the brand-level Letter of Authorization attachment (`{ present, fileName, fileUrl }`; `powerOfAttorney` is deprecated), and `trademarkRegistrations` — every brand-level trademark on file with its issuing office, registration number, and (when uploaded) a `certificateFileUrl` link to the certificate PDF. Soft-deleted brands are excluded. Brand counts per organization are typically <500, so the endpoint returns the full set in one response (no pagination).
organization_create0 of 6 parameters describedCreate a new organization with baseline configuration and return an API key for accessing ChainPatrol services. This endpoint requires authentication with a valid Immunefi API key. Organization slugs will be automatically prefixed with 'immunefi-' (or 'immunefi-test-' when using a test API key) to prevent name clashes. The endpoint validates that the requested slug doesn't conflict with any existing organizations (checking bare slug, 'immunefi-{slug}', and 'immunefi-test-{slug}' variations). The organization will be created with standard monitoring and detection features enabled. Returns the organization details, API key, owner information, and direct dashboard URL.
organization_metrics_get8 of 9 parameters describedGet metrics for your organization with optional date range and brand filtering. Organization is determined from your API key.
organization_proposals_review9 of 9 parameters describedRecords your organization's decision on a proposal that is waiting on you — one ChainPatrol escalated to you, or one on a report you submitted yourself. These are exactly the proposals your Review page shows and the ones `GET /organization/reports?needsCustomerReview=true` counts; find their IDs in `proposals[].id` on that endpoint. `APPROVE` blocks the asset and takes a `label` (plus a `brandId` for labels that name a specific brand). `REJECT` takes a `rejectReason`. `WATCHLIST` rejects the proposal and parks the asset so it is re-evaluated if it comes back alive. Pass `assetId` alongside `proposalId`; it must match the proposal's current asset or the request returns `409`, which keeps a caller from actioning a proposal it never read. Approvals are held to the same safety checks as the Review page, with no override: an asset that any enabled legitimacy rule marks as legitimate cannot be approved here, and an allowlisted asset cannot be blocked here. Both return `403` and must be handled on the Review page by a person. Rate limited to 10 reviews per organization per day, since a review is not undoable and looping over a queue is easy to do by accident. Exceeding it returns `429`. The limit is shared across all of the organization's API credentials and does not apply to reviews made from the Review page.
organization_reports_get2 of 2 parameters describedAnswers 'what happened to this report?'. Takes a report ID, for example from a report link (app.chainpatrol.io/admin/<slug>/reports/<reportId>), and returns the report, how many evidence files are attached to it, and each of its assets: ChainPatrol's review, the asset's status and whether it was still online when last checked, and your organization's takedown of it. Only your organization's reports: any other ID returns 404. To find reports by filters instead, use `GET /organization/reports`.
organization_reports_list4 of 27 parameters describedAnswers 'which of my organization's reports match these filters?'. Returns full report records — proposals, assets, scans, reporter, SLA — with filtering and pagination, newest first. The organization comes from your API key, or pass `slug` when your credentials can reach more than one. To check whether a report already exists for specific assets before filing a new one, use `POST /reports/search`, which looks reports up by asset content in a single batched call.
organization_threat_examples3 of 3 parameters describedPick a handful of an organization's confirmed threats that best show what ChainPatrol found, with the screenshot shown for each: domains and social accounts first, then detailed screenshots, spread across asset types. Includes threats confirmed while protection is not active, so it works for prospects. Built for sales and reporting tools that summarise a threat hunt.
organization_threats_list5 of 5 parameters describedList every asset your organization has reported, with the lifecycle state of each investigation: report opened, escalated, blocklisted, takedown submitted, takedown completed. Built for threat-intel platforms that poll for changes and upsert on asset ID. Supports pagination.
organization_watchlist_list8 of 8 parameters describedList the assets ChainPatrol is watching for your organization: reported assets that were not blocked — typically dead, parked or lacking evidence — and are re-scanned so they can be blocked if they turn malicious. Matches the `threatsWatchlisted` count in `/metrics/summary`. Set `includeTotal` for the count; supports pagination.
report_create10 of 13 parameters describedCreate a new report on ChainPatrol for a particular organization
report_search_external3 of 4 parameters describedAnswers 'do reports already exist for these specific assets?'. Takes a batch of asset contents, normalizes each one the way ChainPatrol normalizes assets, and returns the reports covering them along with which of your assets each report matched. Use it to avoid filing a duplicate before calling `POST /report/create`. To browse or filter an organization's reports instead — by status, asset type, brand, date, review state — use `GET /organization/reports`, which returns the full report records with pagination.
scan_results2 of 2 parameters describedGet detailed scan results including enrichments, rules/checks results, and labels for a specific asset scan.
staff_organization_create4 of 4 parameters describedCreate an organization exactly as ChainPatrol staff do from the app: the owner and the calling staff user are added as members, default asset groups and any initial brands are created, and the website and official assets are allowlisted. Only ChainPatrol staff can call this endpoint, with a staff session or a staff user API key; organization API keys and customer accounts receive 403. The website and official assets are allowlisted automatically, except any that are currently BLOCKED: those are skipped and listed in `skippedAssets`.
staff_ranger_hunt_results2 of 2 parameters describedThe brand profile, narrative and findings of a hunt. `ready` is false until the hunt is done. Findings carry the evidence, the judge's and skeptic's rulings and whether ChainPatrol already blocks the target, so a reviewer can drop the noise before filing anything with `POST /report/create`. Only ChainPatrol staff can call this endpoint.
staff_ranger_hunt_start4 of 4 parameters describedStart a Ranger hunt for a brand: it builds a brand profile, searches the web, social platforms and ChainPatrol's detection sources for lookalikes and scams, verifies each lead and has a skeptic review them. A hunt takes several minutes. It returns a `huntId` at once; poll `/staff/ranger/hunts/{huntId}` for progress and read `/staff/ranger/hunts/{huntId}/results` when it is done. A hunt started here writes nothing to any organization (no assets, reports or threats): the caller reviews the findings and files the good ones. Only ChainPatrol staff can call this endpoint, with a staff session or a staff user API key; organization API keys and customer accounts receive 403.
staff_ranger_hunt_status1 of 1 parameter describedProgress of a hunt started with `POST /staff/ranger/hunts`: its status, the step it is on, how many leads are verified, and what each hunter is doing. `resultsReady` turns true when the report can be read. Only ChainPatrol staff can call this endpoint.
takedowns_list17 of 17 parameters describedList takedowns for an organization. Authenticate with an API key (the org is derived from the key) or with a user session (pass `organizationSlug` in the request body).
threats_list8 of 8 parameters describedList threats for an organization using API key authentication
user_meno parametersGet details of currently logged in user
user_me_update0 of 3 parameters describedUpdate the currently authenticated user's profile and settings
user_org_get1 of 1 parameter describedFetch a single organization by slug. Returns the same per-organization shape as `/user/orgs` (id, name, slug, avatarUrl, subscriptionStatus, services flags, integration connection status, `obligatoryAdminApproval`, `legalDocuments`, and `trademarkRegistrations`). The `integrations` object shows which third-party integrations are connected: `slack`, `discord`, `vercel`, `intercom`, and `moderation` are booleans; `telegram` is `{ connected, groupCount }`. The `legalDocuments` object reports whether the org's Letter of Authorization is on file along with a direct `fileUrl` to view it when present (`powerOfAttorney` is deprecated). `trademarkRegistrations` returns every org-level trademark on file with its issuing office, registration number, and (when uploaded) a `certificateFileUrl` link to the certificate PDF — an empty array means no trademarks are recorded for the org. Access requires the caller to have permission for the org: org-scoped API keys must match the slug; user sessions and user-scoped API keys need an active OrganizationMembership unless the caller is staff. Soft-deleted organizations are excluded.
user_orgs1 of 5 parameters describedList organizations accessible to the current user along with each org's subscription status, which services (reporting, reviewing, protection, takedowns, detection, dark web monitoring) are enabled, integration connection status (Slack, Discord, Telegram, Vercel, Intercom, Moderation API), whether Obligatory Organization Admin Approval is enabled, the org-level Letter of Authorization attachment, and every org-level trademark registration on file. Each service exposes an `active` flag; **only `takedowns` additionally exposes `automated`**. The `integrations` object shows which third-party integrations are connected: `slack`, `discord`, `vercel`, `intercom`, and `moderation` are booleans; `telegram` is `{ connected, groupCount }` since an org can have multiple Telegram groups. The `legalDocuments` block has a `letterOfAuthorization` entry with `{ present, fileName, fileUrl }` (`powerOfAttorney` is deprecated). `trademarkRegistrations` is the full list of org-level trademarks with their issuing office, registration number, and (when uploaded) a `certificateFileUrl` link — use it to identify which customers have or have not added trademarks. Optional `subscriptionStatus`, `services`, and `obligatoryAdminApproval` filters narrow the result server-side. `subscriptionStatus` defaults to the live set (PROSPECT/POC/ACTIVE/INTEGRATION/PROTECTION); pass INACTIVE explicitly to include churned organizations.
validateno parametersValidates if the provided API key is valid for Zapier integration
webhook_config5 of 5 parameters describedCreate and configure a webhook for an organization to receive real-time notifications for asset status updates and new suspected threats. Requires a valid API key with access to the specified organization.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.