Skip to content

Datasource Wholesale Background Check API MCP server

app.datasourcecorp/wholesaledatasourcecorp.appstreamable-httpv1.0.0Scanned

Datasource wholesale background check API docs. Sandbox tools: sandbox.datasourcecorp.app/mcp

7 tools: 1 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 1 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Datasource Wholesale Background Check API MCP server can do

The Datasource Wholesale Background Check API MCP server is published by datasourcecorp.app, a domain the MCP Registry verified. It has 7 tools. It can create or change data (1 tool: get_error), but cannot delete data. 6 tools only read.

1 tool reads private data (search_docs); 2 tools bring in text other people can write (list_operations and get_error).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.0.

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.

7 tools

Changes things 1Claude Code: ask
  • get_errorOne error code from the error catalog: its HTTP status, what it means, what to do, and whether a retry is safe.Reads text others write1 finding

    Why it is in this group

    • The name "get_error" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "get_error" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_error" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    One error code from the error catalog: its HTTP status, what it means, what to do, and whether a retry is safe. Pass the `code` from a problem details body (e.g. client_not_found).

    Annotations the server declares

    • title: Get an error code
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 6Show 6 read-only tools
  • get_guide_sectionOne section of the integration guide, by heading or number (e.g.No findings

    Why it is in this group

    • The name "get_guide_section" says "get": a word for reading.
    Description, as the server wrote it
    One section of the integration guide, by heading or number (e.g. 'Webhooks', '9', 'Testing in the sandbox'). Without a match, lists the sections.

    Annotations the server declares

    • title: Read a guide section
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_operationFull details of one API operation: description, parameters, request body fields, every response and JSON examples (the same text as its section of /llms-full.txt).No findings

    Why it is in this group

    • The name "get_operation" says "get": a word for reading.
    Description, as the server wrote it
    Full details of one API operation: description, parameters, request body fields, every response and JSON examples (the same text as its section of /llms-full.txt). Pass its operationId from list_operations (e.g. GetCheck), or 'METHOD /path'.

    Annotations the server declares

    • title: Get one API operation
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_webhookOne webhook event: when it is sent, its payload fields and an example (e.g.No findings

    Why it is in this group

    • The name "get_webhook" says "get": a word for reading.
    Description, as the server wrote it
    One webhook event: when it is sent, its payload fields and an example (e.g. check.updated). Signature, retry and ordering rules are in the guide's webhooks section.

    Annotations the server declares

    • title: Get one webhook event
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_operationsLists every operation of the API (operationId, HTTP method, path, summary), grouped by tag.Reads text others writeNo findings

    Why it is in this group

    • The name "list_operations" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Lists every operation of the API (operationId, HTTP method, path, summary), grouped by tag. Then call get_operation for one operation's full details.

    Annotations the server declares

    • title: List API operations
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_webhooksLists every webhook event we send (event name and summary).No findings

    Why it is in this group

    • The name "list_webhooks" says "list": a word for reading.
    Description, as the server wrote it
    Lists every webhook event we send (event name and summary). Then call get_webhook for its fields and an example payload.

    Annotations the server declares

    • title: List webhook events
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_docsSearches the integration guide, error catalog, changelog, operations and webhooks.Reads private dataNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    Description, as the server wrote it
    Searches the integration guide, error catalog, changelog, operations and webhooks. Returns the best-matching sections with a snippet and a link; read one in full with get_guide_section, get_error, get_operation or get_webhook.

    Annotations the server declares

    • title: Search the docs
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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 Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 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://api.datasourcecorp.app/mcp: tools/list returned 7 tools to an anonymous client, including get_error (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_error" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_error" says "get": a word for reading.

    What this check looks for

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.

Install

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

claude mcp add --transport http wholesale https://api.datasourcecorp.app/mcp
claude mcp add --transport http wholesale https://api.datasourcecorp.app/mcp

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__wholesale__list_operations",
      "mcp__wholesale__get_operation",
      "mcp__wholesale__search_docs",
      "mcp__wholesale__list_webhooks",
      "mcp__wholesale__get_webhook",
      "mcp__wholesale__get_guide_section"
    ],
    "ask": [
      "mcp__wholesale__get_error"
    ],
    "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 wholesale. Review it before you use it.

Capability tags behind 3 rules
  • mcp__wholesale__list_operations untrusted-input
  • mcp__wholesale__search_docs private-data
  • mcp__wholesale__get_error untrusted-input

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://radar.anlyon.com/api/v1/servers/app.datasourcecorp/wholesale/verify?hash=97dfe15c8229ba3299da3669b548381c5eea61ea01b3d06c6381b7b0e1c6c8e6" | jq -e '.changed == false'

Pinned hash 97dfe15c8229, from Nov 14, 2026, 18:17 UTC.

Watch

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

https://radar.anlyon.com/servers/app.datasourcecorp/wholesale/changes.xml

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

Badge

Anlyon Radar badge for app.datasourcecorp/wholesale
[![Anlyon Radar](https://radar.anlyon.com/badge/app.datasourcecorp/wholesale.svg)](https://radar.anlyon.com/servers/app.datasourcecorp/wholesale)

Source: MCP Registry. Synced Nov 14, 2026, 18:17 UTC.

Datasource Wholesale Background Check API MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Datasource Wholesale Background Check API MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Datasource Wholesale Background Check API MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Datasource Wholesale Background Check API MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Datasource Wholesale Background Check API MCP server have?

7 tools: 1 write, 6 read. get_error, list_operations, get_operation, search_docs, list_webhooks, get_webhook and get_guide_section.

Does the Datasource Wholesale Background Check API MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Datasource Wholesale Background Check API MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Datasource Wholesale Background Check API MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.