mcp-registry/com.jojapi/whatsapp-wyjbao · v1.0.0
As of 2026-10-27 02:49 UTC, the Jojapi Whatsapp Wyjbao MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
WhatsApp: The WhatsApp Profile Data API lets you programmatically fetch a user’s profile picture.
Point your MCP client at this streamable-http endpoint: https://mcp.jojapi.com/whatsapp-wyjbao
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
In the last 30 days: 3 tool(s) removed and 0 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.jojapi%2Fwhatsapp-wyjbao/fixes
{
"name": "get_v1_channel",
"description": "A WhatsApp channel by its invite link or code: name, description, follower count (`channelMetadata.size`), verification, creation time and settings. Looking does not follow the channel. Group: Channels. Billing per call: 1 Credits.",
"inputSchema": {
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"example": "https://whatsapp.com/channel/0029VaAb12Cd34Ef56Gh78Ij90",
"description": "The channel's link (`https://whatsapp.com/channel/…`) or just its code."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Channel"
}{
"name": "get_v1_channel_messages",
"description": "The latest posts of a WhatsApp channel, newest last, with their text, type, time, links and whether they carry media. Does not follow the channel. Group: Channels. Billing per call: 2 Credits.",
"inputSchema": {
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"example": "https://whatsapp.com/channel/0029VaAb12Cd34Ef56Gh78Ij90",
"description": "The channel's link (`https://whatsapp.com/channel/…`) or just its code."
},
"limit": {
"type": "integer",
"default": 20,
"description": "How many of the latest posts to return, 1–100. Default 20."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Channel Posts"
}{
"name": "get_v1_channels_search",
"description": "WhatsApp's channel directory: channels whose name matches `query`, in the countries asked for, or without a query the directory's recommended, trending, popular or new channels. Each channel comes with its follower count, verification, description and invite code (use it with Get Channel and Get Channel Posts). Channels the lookup account follows are not listed. Group: Channels. Billing per call: 1 Credits.",
"inputSchema": {
"type": "object",
"properties": {
"view": {
"enum": [
"recommended",
"trending",
"popular",
"new"
],
"type": "string",
"default": "recommended",
"description": "Which directory list to browse when there is no query."
},
"limit": {
"type": "integer",
"default": 20,
"description": "How many channels to return, 1–50. Default 20."
},
"query": {
"type": "string",
"example": "news",
"description": "Text to look for in channel names, up to 100 characters. Without it, `view` decides what is listed."
},
"country": {
"type": "string",
"example": "TR,DE",
"description": "ISO 3166-1 alpha-2 country codes, comma-separated (up to 10). Default `US`."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Search Channels"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.jojapi/whatsapp-wyjbao"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.jojapi/whatsapp-wyjbao"}) over MCP.
get_v1_channels_search ~308 tokensget_v1_number_profile ~250 tokensget_v1_group_invite ~212 tokensget_v1_channel_messages ~177 tokensget_v1_number_check ~165 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.jojapi%2Fwhatsapp-wyjbao?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.jojapi%2Fwhatsapp-wyjbao?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jojapi%2Fwhatsapp-wyjbao.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jojapi%2Fwhatsapp-wyjbao.svg :target: https://glimind.com/server/mcp-registry%2Fcom.jojapi%2Fwhatsapp-wyjbao?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4c685e18de18e23a…, first seen 2026-10-20, included at leaf 34447 of 76,918. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable search servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 02:49 UTC, the Jojapi Whatsapp Wyjbao MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
Jojapi Whatsapp Wyjbao MCP server advertises 6 tools, including get_v1_channel, get_v1_channel_messages, get_v1_channels_search, get_v1_group_invite, get_v1_number_check.
Point your MCP client at this streamable-http endpoint: https://mcp.jojapi.com/whatsapp-wyjbao
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.