FirmLedger
REMOTE · MCP.FIRMLEDGER.CO.KE · SCANNED SEP 29
FirmLedger: search and verify businesses. Free needs no key; Pro adds contacts, news, jobs.
Available components
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (set_lead_status). See how to fix → View diagnostics → Fail
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5702 tokens (~123/item across 46 items; 46 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the FirmLedger MCP server?
FirmLedger is a hosted endpoint at https://mcp.firmledger.co.ke/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 · mcp.firmledger.co.ke
claude mcp add --transport http ke-co-firmledger-firmledger 'https://mcp.firmledger.co.ke/mcp'
{
"mcpServers": {
"ke-co-firmledger-firmledger": {
"url": "https://mcp.firmledger.co.ke/mcp"
}
}
} {
"servers": {
"ke-co-firmledger-firmledger": {
"type": "http",
"url": "https://mcp.firmledger.co.ke/mcp"
}
}
} [mcp_servers.ke-co-firmledger-firmledger] url = "https://mcp.firmledger.co.ke/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ke-co-firmledger-firmledger": {
"type": "remote",
"url": "https://mcp.firmledger.co.ke/mcp",
"enabled": true
}
}
} openclaw mcp add ke-co-firmledger-firmledger --url 'https://mcp.firmledger.co.ke/mcp' --transport streamable-http
mcp_servers:
ke-co-firmledger-firmledger:
url: "https://mcp.firmledger.co.ke/mcp" {
"McpServers": {
"ke-co-firmledger-firmledger": {
"Transport": "http",
"Url": "https://mcp.firmledger.co.ke/mcp"
}
}
} assistant mcp add ke-co-firmledger-firmledger -t streamable-http -u 'https://mcp.firmledger.co.ke/mcp'
{
"mcpServers": {
"ke-co-firmledger-firmledger": {
"type": "http",
"url": "https://mcp.firmledger.co.ke/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Sept 26 64
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 29 Sept 2026 · Probed https://mcp.firmledger.co.ke/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.firmledger.co.ke | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6dc1c2729276ecddc713ba32acb64a2e2f1 |
| SANs: mcp.firmledger.co.ke | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.firmledger.co.ke. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ke. | present | 17597 | 8 | Verified |
| co.ke. | absent | Delegated | ||
| firmledger.co.ke. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.firmledger.co.ke/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.firmledger.co.ke/mcp | HTTPS enforced | 301 | https://mcp.firmledger.co.ke/mcp |
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 →
check_domain Check whether a website is listed (Pro) ~63
FirmLedger Pro. Given a website domain or URL, report whether an approved FirmLedger record uses it and return that record — useful for "is this site legit?" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain such as "example.co.ke" or a full URL. |
No output schema declared.
No examples provided.
compare_listings Compare FirmLedger listings side by side ~95
Compare 2 to 4 approved FirmLedger companies side by side: entity type, category, location, founded, team size, website, tagline, date registered, ownership, tick, confidence and sponsored status — the same rows as the FirmLedger comparison page. Use after search_listings when the user wants to weigh companies against each other.
| Name | Type | Req | Description |
|---|---|---|---|
| listings | array | yes | 2 to 4 companies (slugs are best). |
No output schema declared.
No examples provided.
connection_status Check FirmLedger connection access ~48
Report what this FirmLedger connection can do: Free or Pro access, authentication and active free-trial status, and which tools and fields are available. Use when the user asks why something is locked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_support_ticket Open a support ticket ~116
Open a FirmLedger support ticket for the user. Categories: billing, technical, listing, account, verification, other. Requires the user's confirmation of the exact subject and message.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The issue in a few sentences. |
| category | string | yes | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| subject | string | yes | – |
No output schema declared.
No examples provided.
create_webhook Create a webhook destination ~134
Register a webhook on the user’s account after explicit confirmation. Listing events will be sent to this URL. Requires Pro (including a free trial) and write:account. The signing secret is returned only once; keep it private.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| events | array | yes | – |
| label | string | – | – |
| url | string | yes | Public HTTPS destination for signed events. |
No output schema declared.
No examples provided.
export_watchlist_csv Export my watchlist as CSV ~51
The user's watchlist as CSV text (name, category, type, location, contact details, tech stack, verified owner, confidence, watched since) — the same file as the dashboard's Export button.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_analytics Read my audience analytics ~83
Audience analytics for the user's own listings — views today/7/30 days/total, unique visitors, profile and website clicks, leads, the 30-day funnel, top visitor locations and per-listing views. The same numbers as Dashboard → Audience analytics.
| Name | Type | Req | Description |
|---|---|---|---|
| listing | string | – | Optional: one of the user's listings. Omit for all of them combined. |
No output schema declared.
No examples provided.
get_api_status REST API v1 status for this key ~129
The state of the FirmLedger REST API for this account and API key, as /api/v1/me and /api/v1/usage answer it: identity, plan and free-trial status, the key's scopes, live per-minute read/write budgets, durable usage aggregates and the endpoint catalogue. Also states plainly that the MCP connector and REST API v1 are the same platform API — one account, one key, one Pro entitlement — and exactly what happens to API and MCP access when a free trial ends.
| Name | Type | Req | Description |
|---|---|---|---|
| key_prefix | string | – | Optional: focus on one key by its prefix. |
No output schema declared.
No examples provided.
get_lead Read one lead conversation ~55
One conversation from the Leads inbox with the inquirer's details and every message, oldest first. Use before reply_to_lead so the reply fits the thread.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | integer | yes | lead_id from list_leads. |
No output schema declared.
No examples provided.
get_listing Get a FirmLedger company profile ~131
The public FirmLedger profile of one company: description, category, location, verification state (tick, how ownership was proved, when it was last checked), confidence and health scores, sources, recent moderated news headlines and the open jobs count. With FirmLedger Pro it also includes website, email, phone, social links, key people, timeline and technology — the same line the website draws.
| Name | Type | Req | Description |
|---|---|---|---|
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
No output schema declared.
No examples provided.
get_my_listings List my FirmLedger listings ~49
The listings this account owns or submitted, with moderation status, tick, scores, Pro perks, sponsorship, jobs and new-lead counts. Use first when the user refers to "my listing".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_news Get moderated company news (Pro) ~110
FirmLedger Pro. Recent moderated news headlines about one company with dates, publishers and links — the same accuracy-gated stories shown on the profile's news panel.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Stories to return (1-12).. Integer or numeric string, clamped to 1–12. |
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
No output schema declared.
No examples provided.
get_notifications Read my notifications ~48
The user's in-app FirmLedger notifications, newest first, with the unread count. Set unread_only for just the unread ones.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| unread_only | boolean | – | – |
No output schema declared.
No examples provided.
get_relationships Get a company's relationship graph (Pro) ~107
FirmLedger Pro. The recorded relationship graph of one company: founders, investors, parent companies, subsidiaries, products, services and partners — plus the reverse edges (companies it founded or invested in). Only relationships recorded by the verified owner or moderators; nothing is inferred.
| Name | Type | Req | Description |
|---|---|---|---|
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
No output schema declared.
No examples provided.
get_watchlist Read my watchlist ~21
The companies the user watches on FirmLedger, newest first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_ad_packages List FirmLedger advertising packages ~52
The current Sponsored-placement advertising packages with price, billing and duration. With an API key it also lists the user's own listings and which of them can be advertised or are already sponsored. Use before prepare_advertising.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_api_keys List my API keys ~47
The account's API keys with label, prefix, scopes, usage totals and last use — never a raw key. Use it to name a key before revoking or re-scoping it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories List FirmLedger categories ~30
Every FirmLedger category with its number of approved listings. Use to pick a valid category for search_listings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_countries List countries on FirmLedger ~26
The countries present in the FirmLedger directory, each with its number of approved listings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jobs List open jobs (Pro) ~150
FirmLedger Pro. Open roles at approved FirmLedger companies, filtered by company and/or location and keyword: title, company, location, posted date and where to apply. Jobs on unapproved listings never appear.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional company (slug, exact name, FirmLedger ID or profile URL). |
| limit | – | – | limit. Integer or numeric string, clamped to 1–25. |
| location | string | – | Optional location, e.g. "Nairobi" or "Kenya" or "Remote". |
| offset | – | – | offset. Integer or numeric string, clamped to 0–10000. |
| query | string | – | Optional keyword in the job title or description. |
No output schema declared.
No examples provided.
list_leads List my leads ~99
The user's FirmLedger Leads inbox: inquiries received on their listings (box "received", the default), archived ones ("archived"), or inquiries they sent to other businesses ("sent"). Filter by status or listing; paginated.
| Name | Type | Req | Description |
|---|---|---|---|
| box | string | – | – |
| limit | integer | – | – |
| listing | string | – | Optional: only leads for this listing of the user's. |
| page | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_my_tickets Read my support tickets ~52
The user's FirmLedger support tickets. Pass a ticket reference to read that ticket's full conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket | string | – | Optional ticket reference, e.g. "TK-1A2B3C". |
No output schema declared.
No examples provided.
list_plans List FirmLedger Pro plans ~49
The current FirmLedger Pro offers with price, billing and duration. With an API key it also says whether this account is already on Pro and whether a free trial is available. Use before prepare_upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhooks List my webhook destinations ~72
The account's webhook destinations with events, category filters, active state and signing-secret prefix — plus recent deliveries (status, HTTP code, attempts, last error) when a webhook id is given.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| webhook_id | integer | – | Optional: one destination, with its recent deliveries. |
No output schema declared.
No examples provided.
manage_api_keys Manage my API keys ~188
Create an API key (the raw key is returned once), revoke a key, or change a key's scopes — the dashboard's Developer API controls. Requires the user's confirmation. Keys can also carry the AI-assistant scopes (read:account / write:account) that this connector uses.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| key_id | integer | – | revoke/update_scopes: the key id from list_api_keys. |
| key_prefix | string | – | Optional alternative to key_id. |
| label | string | – | create: a name for the key. |
| scopes | array | – | Scope ids. Required for update_scopes; create defaults to the standard scopes. |
No output schema declared.
No examples provided.
manage_job Edit, close or remove my job ~156
Manage a job owned by the member: edit its title, type, location, apply link or description, close it, or permanently remove it. Editing a live or closed role returns it to moderation before it is public again. Requires the user’s confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| apply_url | string | – | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| description | string | – | – |
| job_id | integer | yes | – |
| location | string | – | – |
| role_type | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
manage_lead Archive, restore or delete a lead conversation ~109
Archive a conversation out of the business inbox, restore it, or delete it permanently — the dashboard's conversation controls. Requires the user's confirmation (deleting is irreversible).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| lead_id | integer | yes | The lead id from list_leads. |
No output schema declared.
No examples provided.
manage_webhooks Manage my webhook destinations ~190
Create, update, pause, resume, rotate the signing secret of, test, retry a delivery for, or delete a webhook destination on the user's account — the same operations as Dashboard → Developer API. Secrets come back only for create and rotate. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| categories | array | – | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| delivery_id | integer | – | retry_delivery: which delivery to retry. |
| events | array | – | create/update: event types to subscribe to. |
| label | string | – | – |
| url | string | – | create/update: the receiver URL (https in production). |
| webhook_id | integer | – | Required for every action except create. |
No output schema declared.
No examples provided.
mark_notifications_read Mark notifications as read ~93
Mark one notification (notification_id) or all of them (all: true) as read. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| notification_id | integer | – | – |
No output schema declared.
No examples provided.
post_job Post a job on my listing ~167
Submit a job opening on one of the user's listings (the listing needs active Pro perks; up to 5 open or pending roles). Like the dashboard form, it goes to moderation first and is published after approval. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string | yes | Full https:// link to the job post or careers page. |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| description | string | yes | – |
| listing | string | yes | One of the user's own listings. |
| location | string | yes | City, or "Remote". |
| role_type | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
prepare_advertising Prepare a FirmLedger advertising checkout link ~121
Does NOT charge anything. Checks that the listing belongs to this account and is approved, then returns a personal link to FirmLedger's own checkout for the chosen Sponsored-placement package. The user reviews and pays there themselves; you can never complete or confirm a payment. If the user says "yes, do it", give them the link again.
| Name | Type | Req | Description |
|---|---|---|---|
| listing | string | yes | One of the user's own approved listings (see get_my_listings or list_ad_packages). |
| package | string | yes | The package id from list_ad_packages (or its exact name). |
No output schema declared.
No examples provided.
prepare_listing_claim Prepare a listing ownership claim ~112
Free. Prepare a link to claim an approved listing using DNS TXT, HTML meta tag or site badge. Creates nothing and never grants ownership. The user signs in, generates a token, installs the proof on the business domain and verifies it on FirmLedger.
| Name | Type | Req | Description |
|---|---|---|---|
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
| method | string | – | – |
No output schema declared.
No examples provided.
prepare_listing_submission Prepare a FirmLedger listing submission link ~130
Does NOT create anything. Returns a link to the real FirmLedger submission form with the company name, website and (optional) category, country and city pre-filled. The user opens it, signs in, completes the remaining fields, reviews everything and submits it themselves. Also reports if the company is already listed, so nothing is submitted twice.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category. |
| city | string | – | Optional city. |
| country | string | – | Optional country. |
| name | string | yes | Company name. |
| website | string | – | Company website, e.g. "example.co.ke". |
No output schema declared.
No examples provided.
prepare_upgrade Prepare a FirmLedger Pro checkout link ~139
Does NOT charge anything. Returns a personal link to FirmLedger's own checkout for the chosen Pro plan (optionally with a promo code). The user opens it, signs in, reviews the order on FirmLedger and pays on the secure Lemon Squeezy checkout themselves. You can never complete or confirm a payment and must never ask for card details; if the user says "yes, do it", give them the link again. Without an API key it returns the pricing page instead.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | – | The plan id from list_plans (or its exact name). |
| promo_code | string | – | Optional promo code the user gave you. |
No output schema declared.
No examples provided.
refresh_listing_news Refresh my listing's news ~106
Look for new coverage of one of the user's approved listings with the same accuracy rules and moderation as the dashboard's "Refresh news" (once a minute per listing). Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| listing | string | yes | One of the user's own approved listings. |
No output schema declared.
No examples provided.
refresh_listing_scores Refresh my listing's scores ~100
Recompute the confidence, health and completeness scores of one of the user's listings from its current record — the dashboard's "Re-align scores". Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| listing | string | yes | One of the user's own listings. |
No output schema declared.
No examples provided.
refresh_listing_tech Refresh my listing's technology snapshot ~95
Scan the website of one of the user's listings and refresh its technology snapshot — the dashboard's "Refresh tech". Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| listing | string | yes | One of the user's own listings. |
No output schema declared.
No examples provided.
reply_to_lead Reply to a lead ~124
Send a reply in one of the user's lead conversations, exactly as the Reply box on the website does (the other party is notified). Requires the user's confirmation: the first call returns the exact message for them to approve.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| lead_id | integer | yes | – |
| message | string | yes | The reply text, written or approved by the user. |
No output schema declared.
No examples provided.
reply_to_ticket Reply to an open support ticket ~145
Send a reply in one of the user's own support tickets — the same thread the dashboard shows, and the same message an agent answers. Closed tickets cannot take replies. Requires the user's confirmation of the exact text.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| message | string | yes | The reply text, written or approved by the user. |
| ticket | string | yes | The ticket reference (e.g. TK-1A2B3C) or its id, from list_my_tickets. |
No output schema declared.
No examples provided.
request_listing_removal Request removal of my listing ~116
Send a removal request for a listing the user owns or originally submitted. A moderator reviews it; nothing is removed until they accept. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| listing | string | yes | A listing the user owns or submitted. |
| reason | string | yes | Why it should be removed (20+ characters). |
No output schema declared.
No examples provided.
search_listings Search FirmLedger listings ~244
Search approved FirmLedger company records by name or keyword, category, country, city and verified status. Returns a short list (name, category, location, verified flag, tick, confidence score, one-line description) plus the accurate total, for picking the right company before calling get_listing. Use city for places like "Nairobi" and country for "Kenya".
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category name, e.g. "Fintech". Call list_categories for valid names. |
| city | string | – | City or region, e.g. "Nairobi". |
| country | string | – | Country name, e.g. "Kenya". |
| limit | – | – | Results per page (1-25).. Integer or numeric string, clamped to 1–25. |
| offset | – | – | Results to skip, for paging (use next_offset).. Integer or numeric string, clamped to 0–10000. |
| query | string | – | Company name or keyword (matched against name, tagline, description, tags and city). |
| type | string | – | Entity type. |
| verified_only | – | – | Only ownership-verified records (boolean or the string true/false). |
No output schema declared.
No examples provided.
set_lead_status Change a lead's status ~94
Move a lead in the user's business inbox to new, contacted, qualified, won or lost. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| lead_id | integer | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
start_lead Contact a claimed business ~195
Start a new FirmLedger Leads conversation with another approved, claimed business. The signed-in member email is used automatically, the business email stays private, and the owner is notified in their Leads inbox. Requires the user’s confirmation of the exact inquiry.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
| looking_for | string | – | Optional short subject or what the member needs. |
| message | string | yes | – |
| name | string | – | Optional sender name; defaults to the member profile name. |
| phone | string | – | – |
No output schema declared.
No examples provided.
update_my_listing Edit one of my listings ~303
Change fields on a listing the user owns (name, tagline, description, website, email, phone, country, city, region, address, logo_url, founded, size, tags, socials) — the same service the dashboard edit form and PUT /api/v1/my/listings/:id use, including the re-moderation rule when the core record changes. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| city | string | – | – |
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| country | string | – | – |
| description | string | – | – |
| string | – | – | |
| founded | string | – | – |
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
| logo_url | string | – | – |
| name | string | – | – |
| phone | string | – | – |
| region | string | – | – |
| size | string | – | – |
| socials | – | – | Social profile links keyed by network; use an empty object to clear. A JSON object string is also accepted. |
| tagline | string | – | – |
| tags | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
watchlist_add Add a company to my watchlist ~122
Add an approved company to the user's watchlist so they are notified when its record changes. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
No output schema declared.
No examples provided.
watchlist_remove Remove a company from my watchlist ~113
Remove a company from the user's watchlist. Requires the user's confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token. |
| listing | string | yes | The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL. |
No output schema declared.
No examples provided.
What is the FirmLedger MCP server?
FirmLedger is an MCP server listed in the public MCP registry as ke.co.firmledger/firmledger. FirmLedger: search and verify businesses. Free needs no key; Pro adds contacts, news, jobs. This page covers its hosted endpoint (https://mcp.firmledger.co.ke/mcp).
Is the FirmLedger MCP server safe to use?
FirmLedger scores 64 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 FirmLedger MCP server expose?
FirmLedger exposes 46 tools: search_listings, get_listing, get_relationships, get_news, list_jobs, and 41 more. Their descriptions and schemas cost roughly 4,979 tokens of context every time the server is loaded.
Does the FirmLedger MCP server require authentication?
No. We connected to FirmLedger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FirmLedger MCP server still maintained?
FirmLedger is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.