_ registry / mcp streamable-http · checked 11h ago

messente-mcp

https://messente.usefulapi.io

Registry code: b04a454cb6b55328

api record

Tools for Messente, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes Messente data. Free plan: 100 tool calls per month. Run messente_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run messente_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run messente_upgrade; it returns a Stripe Checkout link for the user to open.…

endpoint
https://messente.usefulapi.io/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 messente-mcp live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is messente-mcp free to use?
No — it asks for a key or a login before it will serve.
What tools does messente-mcp have?
9 tools: messente_list_blacklist, messente_check_blacklist, messente_get_balance, messente_get_statistics, messente_get_prices, messente_get_delivery_status, messente_lookup_numbers, messente_add_to_blacklist, ….
Is messente-mcp 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
100%

90 days 100%· all time 100%

latency
169ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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.

  • messente_list_blacklist auth-required 11h ago

    List the phone numbers on the account's blacklist (numbers Messente will not send to). Returns the total count and at most `limit` numbers. Messente: GET /phonebook/blacklist.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 2000,
      "minimum": 1,
      "description": "Maximum numbers to return (default 500)."
    },
    "offset": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Skip this many numbers (to page through a long list)."
    }
  }
}
    arguments 18 lines
  • messente_check_blacklist auth-required 11h ago

    Check whether one phone number is on the account's blacklist. Messente: GET /phonebook/blacklist/{phone} (found = blacklisted, 404 = not).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "phone"
  ],
  "properties": {
    "phone": {
      "type": "string",
      "pattern": "^\\+[1-9]\\d{6,14}$",
      "description": "Phone number in E.164 format, e.g. +37251000000."
    }
  }
}
    arguments 14 lines
  • messente_get_balance auth-required 11h ago

    Get the Messente account's remaining SMS credit balance (in EUR). Messente legacy API: GET /get_balance (api2.messente.com).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • messente_get_statistics auth-required never probed

    Get total messages and total price per country for a date range, optionally for some message types. Messente: POST /statistics/reports (a read-only report).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "start_date",
    "end_date"
  ],
  "properties": {
    "end_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "End date, YYYY-MM-DD."
    },
    "start_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Start date, YYYY-MM-DD."
    },
    "message_types": {
      "type": "array",
      "items": {
        "enum": [
          "sms",
          "viber",
          "whatsapp",
          "rcs",
          "hlr"
        ],
        "type": "string"
      },
      "maxItems": 5,
      "description": "Limit the report to these message types."
    }
  }
}
    arguments 35 lines
  • messente_get_prices auth-required never probed

    Get this account's price per SMS part for one country, per mobile network (use it to estimate what messente_send_sms will cost). Messente legacy API: GET /prices.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "country"
  ],
  "properties": {
    "country": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "ISO 3166-1 alpha-2 country code, e.g. EE or GB."
    }
  }
}
    arguments 14 lines
  • messente_get_delivery_status auth-required never probed

    Get the delivery report of a sent message by its omnimessage id (returned by messente_send_sms): per-message status (DELIVRD, UNDELIV, FAILED, ...), error and the price charged. Messente asks not to poll this for every message at scale. Messente: GET /omnimessage/{omnimessage_id}/status.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "omnimessage_id"
  ],
  "properties": {
    "omnimessage_id": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "The omnimessage_id returned when the message was sent."
    }
  }
}
    arguments 15 lines
  • messente_lookup_numbers auth-required never probed

    Number lookup (HLR): is each number valid, ported, roaming, and which network it is on. COSTS CREDITS: Messente charges per number looked up (EUR 0.002 per number in its docs) and the Number Lookup service must be enabled on the account (a fixed monthly fee applies per Messente's docs). Up to 10 numbers per call. Messente: POST /hlr/sync.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "numbers"
  ],
  "properties": {
    "numbers": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\+[1-9]\\d{6,14}$"
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "Phone numbers in E.164 format (1-10)."
    }
  }
}
    arguments 19 lines
  • messente_add_to_blacklist auth-required never probed

    WRITE: add one phone number to the account's blacklist, so Messente will no longer send messages to it. Adding a number already listed is harmless. Messente: POST /phonebook/blacklist.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "phone_number"
  ],
  "properties": {
    "phone_number": {
      "type": "string",
      "pattern": "^\\+[1-9]\\d{6,14}$",
      "description": "Phone number to blacklist, E.164 format, e.g. +37251000000."
    }
  }
}
    arguments 14 lines
  • messente_send_sms auth-required never probed

    WRITE: SENDS REAL SMS TEXT MESSAGES to real people and SPENDS the account's Messente credit (each recipient is charged per SMS part, longer texts use several parts; use messente_get_prices to estimate). SMS only, at most 10 recipients per call, one message per recipient, never to a list. Send only to people who asked to receive it (Messente forbids unsolicited messages). Not undoable. Messente: POST /omnimessage with channel sms, once per recipient.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "to",
    "text"
  ],
  "properties": {
    "to": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\+[1-9]\\d{6,14}$"
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "Recipient phone numbers in E.164 format (1-10)."
    },
    "text": {
      "type": "string",
      "maxLength": 1600,
      "minLength": 1,
      "description": "The message text."
    },
    "sender": {
      "type": "string",
      "pattern": "^[A-Za-z0-9 .+_-]+$",
      "maxLength": 20,
      "minLength": 1,
      "description": "Sender name (alphanumeric, max 11 chars) or number; must be a sender verified on the account. Omit to use the account default."
    }
  }
}
    arguments 33 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 b04a454cb6b55328.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b04a454cb6b55328/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/b04a454cb6b55328/badge.svg)](https://brick.blue/agent/b04a454cb6b55328?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.

_ also on usefulapi.io 131 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

123 more sit on this domain. All of them.