MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Payments & trading

AdminPulse MCP by usefulapi

Read relations, invoices, tasks and documents; create tasks and log interactions in AdminPulse.

Checks passed
13 / 22

1 failed · 8 not measured

Median response
150 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
15

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 150 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name adminpulse-mcp.

  • Pass
    Lists tools

    tools/list returned 15 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 150 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 150 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    62 of 66 parameters have a description (94%). The bar is 80%.

  • Fail
    Safety hints

    1 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:34:45.088713Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using AdminPulse MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http adminpulse-mcp-by-usefulapi https://adminpulse.usefulapi.io/mcp

Capabilities

Tools 15

adminpulse_add_interaction

Log an interaction (for example a call or a note) on a relation. The date is ddMMyyyy and the time is HH:mm. POST /interactions/add.

Discovered
adminpulse_create_task

Create a task for a relation. The deadline is ISO, for example 2026-01-31T00:00:00. Status is the number the API defines. POST /tasks.

Discovered
adminpulse_find_relations_by_name

Quick lookup of relations by name, returning a short list with their ids and unique identifiers. GET /relations/names.

Discovered
adminpulse_get_current_user

Return the AdminPulse user that the API key belongs to (name and email). Good first call to confirm the connection. GET /users/me.

Discovered
adminpulse_get_invoice

Get one invoice by its id (GUID), with its lines and payment status. GET /invoices/{invoiceId}.

Discovered
adminpulse_get_relation

Get one relation with its details. Pass the relation GUID or its unique identifier such as APR00001. GET /relations/{identifier}.

Discovered
adminpulse_get_task

Get one task by its id (GUID), with its status, deadline and relation. GET /tasks/{taskId}.

Discovered
adminpulse_list_companies

List the companies (administrations) that this key can access, with their ids. GET /companies.

Discovered
adminpulse_list_documents

List document metadata (name, type, dates, tags) with paging. Filter by relation or document date range. GET /documents.

Discovered
adminpulse_list_interactions

List logged interactions (calls, meetings, notes) with paging. Filter by relation, type or date. GET /interactions.

Discovered
adminpulse_list_invoices

List sales invoices with paging. Filter by relation, invoice date range, or sent, paid, exported and draft status. GET /invoices.

Discovered
adminpulse_list_registrations

List time or cost registrations with paging. Filter by relation, invoiced state or registration date range. GET /registrations.

Discovered
adminpulse_list_tasks

List tasks with paging. Filter by relation id, deadline range, or main task template. GET /tasks.

Discovered
adminpulse_search_relations

List relations (clients, suppliers and contacts) with paging. Filter by text, relation type (0 company, 1 sole proprietor, 2 person), tags, or include inactive. GET /relations.

Discovered
adminpulse_update_task_status

Set the status of a task found by relation, deadline and task names (no task id needed). Setting the same status again changes nothing. POST /tasks/updateStatus.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected150 ms15