# FirmLedger (remote · mcp.firmledger.co.ke)

FirmLedger: search and verify businesses. Free needs no key; Pro adds contacts, news, jobs.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mcp.firmledger.co.ke`: 64/100 (this document), [markdown](https://verifymcp.io/servers/ke-co-firmledger-firmledger/mcp.md), [page](https://verifymcp.io/servers/ke-co-firmledger-firmledger/mcp)

## Channel facts

- Endpoint: `https://mcp.firmledger.co.ke/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (set_lead_status).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 47 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ke-co-firmledger-firmledger 'https://mcp.firmledger.co.ke/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ke-co-firmledger-firmledger": {
      "url": "https://mcp.firmledger.co.ke/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ke-co-firmledger-firmledger": {
      "type": "http",
      "url": "https://mcp.firmledger.co.ke/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ke-co-firmledger-firmledger]
url = "https://mcp.firmledger.co.ke/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ke-co-firmledger-firmledger": {
      "type": "remote",
      "url": "https://mcp.firmledger.co.ke/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ke-co-firmledger-firmledger --url 'https://mcp.firmledger.co.ke/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ke-co-firmledger-firmledger:
    url: "https://mcp.firmledger.co.ke/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ke-co-firmledger-firmledger": {
      "Transport": "http",
      "Url": "https://mcp.firmledger.co.ke/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ke-co-firmledger-firmledger -t streamable-http -u 'https://mcp.firmledger.co.ke/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-28 (score 64)

First indexed and scored.

## MCP tools (46)

### `search_listings` (~244 tokens)

Search FirmLedger listings

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".

Input parameters:

- `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).

### `get_listing` (~131 tokens)

Get a FirmLedger company profile

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.

Input parameters:

- `listing` (string, required): 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.

### `get_relationships` (~107 tokens)

Get a company's relationship graph (Pro)

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.

Input parameters:

- `listing` (string, required): 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.

### `get_news` (~110 tokens)

Get moderated company news (Pro)

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.

Input parameters:

- `limit`: Stories to return (1-12).. Integer or numeric string, clamped to 1–12.
- `listing` (string, required): 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.

### `list_jobs` (~150 tokens)

List open jobs (Pro)

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.

Input parameters:

- `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.

### `check_domain` (~63 tokens)

Check whether a website is listed (Pro)

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.

Input parameters:

- `domain` (string, required): A domain such as "example.co.ke" or a full URL.

### `list_categories` (~30 tokens)

List FirmLedger categories

Every FirmLedger category with its number of approved listings. Use to pick a valid category for search_listings.

### `list_countries` (~26 tokens)

List countries on FirmLedger

The countries present in the FirmLedger directory, each with its number of approved listings.

### `prepare_listing_submission` (~130 tokens)

Prepare a FirmLedger listing submission link

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.

Input parameters:

- `category` (string): Optional category.
- `city` (string): Optional city.
- `country` (string): Optional country.
- `name` (string, required): Company name.
- `website` (string): Company website, e.g. "example.co.ke".

### `compare_listings` (~95 tokens)

Compare FirmLedger listings side by side

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.

Input parameters:

- `listings` (array, required): 2 to 4 companies (slugs are best).

### `list_plans` (~49 tokens)

List FirmLedger Pro plans

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.

### `list_ad_packages` (~52 tokens)

List FirmLedger advertising packages

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.

### `prepare_upgrade` (~139 tokens)

Prepare a FirmLedger Pro checkout link

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.

Input parameters:

- `plan` (string): The plan id from list_plans (or its exact name).
- `promo_code` (string): Optional promo code the user gave you.

### `prepare_advertising` (~121 tokens)

Prepare a FirmLedger advertising checkout link

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.

Input parameters:

- `listing` (string, required): One of the user's own approved listings (see get_my_listings or list_ad_packages).
- `package` (string, required): The package id from list_ad_packages (or its exact name).

### `get_my_listings` (~49 tokens)

List my FirmLedger listings

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".

### `get_analytics` (~83 tokens)

Read my audience analytics

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.

Input parameters:

- `listing` (string): Optional: one of the user's listings. Omit for all of them combined.

### `list_leads` (~99 tokens)

List my leads

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.

Input parameters:

- `box` (string)
- `limit` (integer)
- `listing` (string): Optional: only leads for this listing of the user's.
- `page` (integer)
- `status` (string)

### `get_lead` (~55 tokens)

Read one lead conversation

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.

Input parameters:

- `lead_id` (integer, required): lead_id from list_leads.

### `get_watchlist` (~21 tokens)

Read my watchlist

The companies the user watches on FirmLedger, newest first.

### `export_watchlist_csv` (~51 tokens)

Export my watchlist as CSV

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.

### `get_notifications` (~48 tokens)

Read my notifications

The user's in-app FirmLedger notifications, newest first, with the unread count. Set unread_only for just the unread ones.

Input parameters:

- `limit` (integer)
- `unread_only` (boolean)

### `list_my_tickets` (~52 tokens)

Read my support tickets

The user's FirmLedger support tickets. Pass a ticket reference to read that ticket's full conversation.

Input parameters:

- `ticket` (string): Optional ticket reference, e.g. "TK-1A2B3C".

### `get_api_status` (~129 tokens)

REST API v1 status for this key

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.

Input parameters:

- `key_prefix` (string): Optional: focus on one key by its prefix.

### `list_webhooks` (~72 tokens)

List my webhook destinations

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.

Input parameters:

- `limit` (integer)
- `webhook_id` (integer): Optional: one destination, with its recent deliveries.

### `list_api_keys` (~47 tokens)

List my API keys

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.

### `start_lead` (~195 tokens)

Contact a claimed business

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.

Input parameters:

- `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, required): 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, required)
- `name` (string): Optional sender name; defaults to the member profile name.
- `phone` (string)

### `reply_to_lead` (~124 tokens)

Reply to a lead

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.

Input parameters:

- `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, required)
- `message` (string, required): The reply text, written or approved by the user.

### `set_lead_status` (~94 tokens)

Change a lead's status

Move a lead in the user's business inbox to new, contacted, qualified, won or lost. Requires the user's confirmation.

Input parameters:

- `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, required)
- `status` (string, required)

### `watchlist_add` (~122 tokens)

Add a company to my watchlist

Add an approved company to the user's watchlist so they are notified when its record changes. Requires the user's confirmation.

Input parameters:

- `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, required): 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.

### `watchlist_remove` (~113 tokens)

Remove a company from my watchlist

Remove a company from the user's watchlist. Requires the user's confirmation.

Input parameters:

- `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, required): 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.

### `create_support_ticket` (~116 tokens)

Open a support ticket

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.

Input parameters:

- `body` (string, required): The issue in a few sentences.
- `category` (string, required)
- `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, required)

### `manage_job` (~156 tokens)

Edit, close or remove my job

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.

Input parameters:

- `action` (string, required)
- `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, required)
- `location` (string)
- `role_type` (string)
- `title` (string)

### `post_job` (~167 tokens)

Post a job on my listing

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.

Input parameters:

- `apply_url` (string, required): 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, required)
- `listing` (string, required): One of the user's own listings.
- `location` (string, required): City, or "Remote".
- `role_type` (string)
- `title` (string, required)

### `mark_notifications_read` (~93 tokens)

Mark notifications as read

Mark one notification (notification_id) or all of them (all: true) as read. Requires the user's confirmation.

Input parameters:

- `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)

### `refresh_listing_scores` (~100 tokens)

Refresh my listing's scores

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.

Input parameters:

- `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, required): One of the user's own listings.

### `refresh_listing_tech` (~95 tokens)

Refresh my listing's technology snapshot

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.

Input parameters:

- `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, required): One of the user's own listings.

### `refresh_listing_news` (~106 tokens)

Refresh my listing's news

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.

Input parameters:

- `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, required): One of the user's own approved listings.

### `request_listing_removal` (~116 tokens)

Request removal of my listing

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.

Input parameters:

- `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, required): A listing the user owns or submitted.
- `reason` (string, required): Why it should be removed (20+ characters).

### `prepare_listing_claim` (~112 tokens)

Prepare a listing ownership claim

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.

Input parameters:

- `listing` (string, required): 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)

### `create_webhook` (~134 tokens)

Create a webhook destination

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.

Input parameters:

- `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, required)
- `label` (string)
- `url` (string, required): Public HTTPS destination for signed events.

### `reply_to_ticket` (~145 tokens)

Reply to an open support ticket

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.

Input parameters:

- `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, required): The reply text, written or approved by the user.
- `ticket` (string, required): The ticket reference (e.g. TK-1A2B3C) or its id, from list_my_tickets.

### `manage_webhooks` (~190 tokens)

Manage my webhook destinations

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.

Input parameters:

- `action` (string, required)
- `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.

### `manage_api_keys` (~188 tokens)

Manage my API keys

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.

Input parameters:

- `action` (string, required)
- `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.

### `update_my_listing` (~303 tokens)

Edit one of my listings

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.

Input parameters:

- `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)
- `email` (string)
- `founded` (string)
- `listing` (string, required): 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)

### `manage_lead` (~109 tokens)

Archive, restore or delete a lead conversation

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).

Input parameters:

- `action` (string, required)
- `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, required): The lead id from list_leads.

### `connection_status` (~48 tokens)

Check FirmLedger connection access

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ke-co-firmledger-firmledger/mcp#diagnostics

## Score history

- 2026-09-29: 64
- 2026-09-28: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.firmledger.co.ke/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ke-co-firmledger-firmledger/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ke-co-firmledger-firmledger/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ke-co-firmledger-firmledger/mcp