com.jojapi/whatsapp-wyjbao
REMOTE · MCP.JOJAPI.COM
WhatsApp: The WhatsApp Profile Data API lets you programmatically fetch a user’s profile picture.
Available components
Last scanned (11 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 958 tokens (~159/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Oct 26 −14
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “post_getAbout” was removed ▼ security
- Tool “post_getProfilePicUrl” was removed ▼ security
- Tool “post_getUserInfo” was removed ▼ security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- New tool “get_v1_channel” functional
- New tool “get_v1_channel_messages” functional
- New tool “get_v1_channels_search” functional
- New tool “get_v1_group_invite” functional
- New tool “get_v1_number_check” functional
- New tool “get_v1_number_profile” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.jojapi.com/whatsapp-wyjbao
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.jojapi.com | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4fdef8b174aa7f510e6f8de60526c223 |
| SANs: mcp.jojapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.jojapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jojapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.jojapi.com/whatsapp-wyjbao | Verified | 200 | |
| http (plaintext) | http://mcp.jojapi.com/whatsapp-wyjbao | HTTPS enforced | 301 | https://mcp.jojapi.com/whatsapp-wyjbao |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_v1_channel Get Channel ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The channel's link (`https://whatsapp.com/channel/…`) or just its code. |
No output schema declared.
No examples provided.
get_v1_channel_messages Get Channel Posts ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The channel's link (`https://whatsapp.com/channel/…`) or just its code. |
| limit | integer | – | How many of the latest posts to return, 1–100. Default 20. |
No output schema declared.
No examples provided.
get_v1_channels_search Search Channels ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country codes, comma-separated (up to 10). Default `US`. |
| limit | integer | – | How many channels to return, 1–50. Default 20. |
| query | string | – | Text to look for in channel names, up to 100 characters. Without it, `view` decides what is listed. |
| view | string | – | Which directory list to browse when there is no query. |
No output schema declared.
No examples provided.
get_v1_group_invite Get Group by Invite Link ~134
What WhatsApp shows anyone who opens a group's invite link: the group's name (`subject`) and description with who set them and when, its size, creation time and creator's country, its settings (announcements only, admin-only edits, join approval), the owner, and a few participants with their phone numbers. Looking does not join the group. A code that is wrong, revoked or expired answers 404 `not_found`. Group: Groups. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The invite link (`https://chat.whatsapp.com/…`) or just its code. |
No output schema declared.
No examples provided.
get_v1_number_check Check Number ~115
Whether a phone number has a WhatsApp account, and its WhatsApp id. A number without an account is a normal answer (`registered: false`), not an error. Group: Numbers. Billing per call: 1 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | The phone number in international format with its country code, e.g. `+14155550123`. Spaces, dashes, brackets, a leading `00` or the WhatsApp id form (`14155550123@c.us`) are accepted. |
No output schema declared.
No examples provided.
get_v1_number_profile Get Profile ~232
Everything WhatsApp shows about the account on a phone number: the contact (`pushname`, the name the person set; `isBusiness`, `verifiedName` and, for business accounts, `businessProfile` with description, categories, website, email, address, opening hours and linked Facebook/Instagram), the about text, the profile picture URL, the account's LID and the number of devices it uses (phone plus WhatsApp Web/desktop). `about` and `profile_picture_url` are `null` when the person hides or never set them; picture URLs expire after a while. A part that could not be read is `null` and named in `unavailable`. A number with no WhatsApp account answers 404 `not_registered`. Group: Numbers. Billing per call: 3 Credits.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | The phone number in international format with its country code, e.g. `+14155550123`. Spaces, dashes, brackets, a leading `00` or the WhatsApp id form (`14155550123@c.us`) are accepted. |
No output schema declared.
No examples provided.
How do I install the com.jojapi/whatsapp-wyjbao MCP server?
com.jojapi/whatsapp-wyjbao is a hosted endpoint at https://mcp.jojapi.com/whatsapp-wyjbao, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.jojapi.com
claude mcp add --transport http com-jojapi-whatsapp-wyjbao 'https://mcp.jojapi.com/whatsapp-wyjbao'
What is the com.jojapi/whatsapp-wyjbao MCP server?
com.jojapi/whatsapp-wyjbao is an MCP server listed in the public MCP registry as com.jojapi/whatsapp-wyjbao. WhatsApp: The WhatsApp Profile Data API lets you programmatically fetch a user’s profile picture. This page covers its hosted endpoint (https://mcp.jojapi.com/whatsapp-wyjbao).
Is the com.jojapi/whatsapp-wyjbao MCP server safe to use?
com.jojapi/whatsapp-wyjbao scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.jojapi/whatsapp-wyjbao MCP server expose?
com.jojapi/whatsapp-wyjbao exposes 6 tools: get_v1_number_check, get_v1_number_profile, get_v1_group_invite, get_v1_channel, get_v1_channel_messages, get_v1_channels_search. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.
Does the com.jojapi/whatsapp-wyjbao MCP server require authentication?
No. We connected to com.jojapi/whatsapp-wyjbao without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.jojapi/whatsapp-wyjbao MCP server still maintained?
com.jojapi/whatsapp-wyjbao is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.