Wiremi Marketing MCP
REMOTE · WIREMI-MARKETING-MCP-PQLQUIJG3Q-UK.A.RUN.APP
Read-only ROSCA and savings-circle answers and calculators, from Wiremi's public facts.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 8 Oct 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified 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
- 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 4 Aug 26 0
- Server version: 1.27.2 → 1.28.1 functional
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://wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | SHA256-RSA | 53da11951e5eb49012fb872c3cb3e54d |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app/mcp | Inconclusive | 404 |
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 →
ask_wiremi ~122
Ask Wiremi anything about ROSCAs, savings circles, the Wiremi Passport, or how Wiremi works, in the user's own words. Routes the question to the best Wiremi answer and always points to where to go next. Use this when the other tools do not exactly match what the user asked. The question text is logged (no other personal data) so Wiremi can see what real people ask and improve its answers, the way Search Console shows real search queries.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
No output schema declared.
No examples provided.
does_rosca_build_credit_canada ~80
Answer whether ROSCA / savings-circle payments build credit history in Canada. The honest answer: not yet directly to a credit bureau, but a Wiremi on-ledger record is the data foundation for a credit-reporting pilot in conversation with a Canadian bureau. Never claims bureau reporting is live. No personal data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_a_rosca_works ~57
Explain the payout mechanics of a ROSCA with a concrete example: fixed contribution each cycle, one member receives the pot per cycle, rotates until everyone has had a turn, interest-free. No personal data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_to_start_a_circle ~51
How to start or join a savings circle on Wiremi: download the app, open Group Savings, set members/amount/frequency, invite. Includes app links. No personal data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rosca_payout ~130
Calculate a ROSCA's payout and schedule. Inputs: number of members (2-60), contribution amount per round, frequency ("weekly"|"biweekly"|"monthly"), and your turn in the rotation (1..members). Returns the pot you receive, your turn date, total you contribute, per-round amount, and the full rotation schedule. Faithful port of the wiremi.ca ROSCA calculator. No personal data.
| Name | Type | Req | Description |
|---|---|---|---|
| contribution | number | yes | – |
| frequency | string | – | – |
| members | integer | yes | – |
| turn | integer | – | – |
No output schema declared.
No examples provided.
rosca_research_report ~127
Headline findings from Wiremi's public-data report, "The State of ROSCAs in the Canadian Diaspora 2026": immigrant population from rotating-savings cultures, the credit-invisibility gap measured by Statistics Canada, why ROSCA payments are invisible to credit bureaus, and the 70-year history of ROSCAs in Canada. Every figure is sourced to public data (Statistics Canada, World Bank, peer-reviewed research). Returns the canonical report URL and PDF so callers can cite the source. No personal data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rosca_vs_loan ~140
Compare a savings circle (ROSCA) against a bank loan for the same goal. Inputs: goal amount (>=100), months (2-60), loan APR percent (0-60). Returns the loan's monthly payment, total repaid, and interest cost, versus the ROSCA's zero interest, plus the honest tradeoff (a loan pays out now; a ROSCA pays on your turn). Faithful port of the wiremi.ca ROSCA-vs-loan tool. No personal data.
| Name | Type | Req | Description |
|---|---|---|---|
| apr | number | yes | – |
| goal | number | yes | – |
| months | integer | yes | – |
No output schema declared.
No examples provided.
what_is_a_rosca ~71
Explain what a ROSCA (rotating savings circle) is. If `term` is given (for example "njangi", "susu", "tanda"), also return that name's cultural origin. Pure public education. No personal data.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | – | – |
No output schema declared.
No examples provided.
what_is_wiremi ~57
What Wiremi is and is not, plus its regulatory registrations. Honest about being ROSCA-first (not primarily remittance), not reporting to bureaus yet, and not operating US payment rails. No personal data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
where_wiremi_operates ~73
Where Wiremi operates. Lists the seven live African funding corridors, states clearly that CAD and US funding rails are NOT live yet (estimated Q3 2026), and notes North American users can download and subscribe but cannot yet fund a wallet or send money. No personal data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Wiremi Marketing MCP server?
Wiremi Marketing MCP is a hosted endpoint at https://wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app/mcp, 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 · wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app
claude mcp add --transport http ca-wiremi-marketing-mcp 'https://wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app/mcp'
What is the Wiremi Marketing MCP server?
Wiremi Marketing MCP is listed in the public MCP registry as ca.wiremi/marketing-mcp. Read-only ROSCA and savings-circle answers and calculators, from Wiremi's public facts. This page covers its hosted endpoint (https://wiremi-marketing-mcp-pqlquijg3q-uk.a.run.app/mcp).
Is the Wiremi Marketing MCP server safe to use?
Wiremi Marketing MCP scores 18 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 Wiremi Marketing MCP server expose?
Wiremi Marketing MCP exposes 10 tools: what_is_a_rosca, how_a_rosca_works, rosca_payout, rosca_vs_loan, does_rosca_build_credit_canada, and 5 more. Their descriptions and schemas cost roughly 908 tokens of context every time the server is loaded.
Does the Wiremi Marketing MCP server require authentication?
Its publisher declares no required credentials for Wiremi Marketing MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Wiremi Marketing MCP server still maintained?
Wiremi Marketing MCP 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.