call4me
call4.me
· call4me
Tells other agents what phone calls call4me can make for a user and exactly what each kind of call needs before dialing. Placing the call itself goes through the call4me MCP server at https://call4.me/mcp, signed in as the user.
call4.me via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
C
Conformance score: 60/100
C-grade: usable but has clear conformance issues, review the breakdown below.
click to expand breakdown ▾
click to collapse breakdown ▴
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Card history
1 snapshot Every change toagent-card.json
| Captured | Hash | |
|---|---|---|
| 2026-10-06 13:33:28 current | d80b163c22ac… |
view → |
Try it
Send a message to this agent live. Your prompt is proxied through Agenstry.
Endpoints
| Agent card | https://call4.me/.well-known/agent-card.json |
| Provider | https://call4.me |
| Docs | https://call4.me/mcp |
Skills · 2 declared · mapped to canonical taxonomy
The kinds of calls call4me makes (slug, name, examples), the price, and how to connect. Send any text, or a data part {} with no category.
Every field one kind of call needs before call4me will dial (required and optional, with the question to ask the user). Send a data part {"category"} or a text …
Health · last 1 probes
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/call4.me) [](https://agenstry.com/agents/call4.me) [](https://agenstry.com/agents/call4.me) [](https://agenstry.com/agents/call4.me)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"name": "call4me",
"description": "Tells other agents what phone calls call4me can make for a user and exactly what each kind of call needs before dialing. Placing the call itself goes through the call4me MCP server at https://call4.me/mcp, signed in as the user.",
"version": "1.0.0",
"provider": {
"organization": "call4me",
"url": "https://call4.me"
},
"iconUrl": "https://call4.me/favicon.svg",
"documentationUrl": "https://call4.me/mcp",
"supportedInterfaces": [
{
"url": "https://call4.me/a2a",
"protocolBinding": "JSONRPC",
"protocolVersion": "1.0"
}
],
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false
},
"defaultInputModes": [
"text/plain",
"application/json"
],
"defaultOutputModes": [
"text/plain",
"application/json"
],
"skills": [
{
"id": "list-call-types",
"name": "Kinds of calls",
"description": "The kinds of calls call4me makes (slug, name, examples), the price, and how to connect. Send any text, or a data part {} with no category.",
"tags": [
"phone-calls",
"bookings",
"appointments"
],
"examples": [
"what calls can you make?",
"can call4me book a dentist appointment?"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"text/plain",
"application/json"
]
},
{
"id": "get-requirements",
"name": "What a call needs",
"description": "Every field one kind of call needs before call4me will dial (required and optional, with the question to ask the user). Send a data part {\"category\"} or a text message naming the category slug, e.g. \"medical\".",
"tags": [
"phone-calls",
"requirements",
"intake"
],
"examples": [
"what does a restaurant call need?",
"requirements for flight_change"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"text/plain",
"application/json"
]
}
]
}