ke.co.firmledger/firmledger

Est-ce que ke.co.firmledger/firmledger est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ke.co.firmledger/firmledger » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 49 outils

• check_domain≈ 167 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    A domain such as "example.co.ke" or a full URL.

  Exemple d'appel

  {"name": "check_domain", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compare_listings≈ 264 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • listings · array · requis
    2 to 4 companies (slugs are best).

  Exemple d'appel

  {"name": "compare_listings", "arguments": {"listings": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• connection_status≈ 135 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "connection_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_support_ticket≈ 277 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • body · string · requis
    The issue in a few sentences.
  • subject · string · requis
  • category · string · requis · billing | technical | listing | account | verification | other
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "create_support_ticket", "arguments": {"body": "texte", "subject": "texte", "category": "billing"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_webhook≈ 328 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • url · string · requis
    Public HTTPS destination for signed events.
  • label · string · optionnel
  • events · array · requis
  • categories · array · optionnel
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "create_webhook", "arguments": {"url": "texte", "events": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• export_watchlist_csv≈ 128 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "export_watchlist_csv", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_analytics≈ 199 tokens

  Audience analytics for the user's own listings — views today/7/30 days/total, distinct hashed visitor signals, profile and website clicks, leads, the 30-day funnel (placements served and browser-measured viewable impressions are separate), top locations and per-listing views. The same numbers as Dashboard → Audience analytics.

  Paramètres, retour & exemple (1)

  Paramètres

  • listing · string · optionnel
    Optional: one of the user's listings. Omit for all of them combined.

  Exemple d'appel

  {"name": "get_analytics", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_api_status≈ 224 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • key_prefix · string · optionnel
    Optional: focus on one key by its prefix.

  Exemple d'appel

  {"name": "get_api_status", "arguments": {"key_prefix": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_connection_status≈ 174 tokens

  Report how this assistant is connected to FirmLedger: public (no sign-in), an API key, or the member's account through sign-in (OAuth). Shows Free or Pro, the trial status, which tools and fields are available, and whether the sign-in token is about to expire. Use it when the member asks whether they are connected or signed in, or why something is locked.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_connection_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_lead≈ 145 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • lead_id · integer · requis
    lead_id from list_leads.

  Exemple d'appel

  {"name": "get_lead", "arguments": {"lead_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_listing≈ 248 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • listing · string · requis
    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.

  Exemple d'appel

  {"name": "get_listing", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_my_listings≈ 126 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_my_listings", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_news≈ 237 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · ? · optionnel
    Stories to return (1-12).. Integer or numeric string, clamped to 1–12.
  • listing · string · requis
    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.

  Exemple d'appel

  {"name": "get_news", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_notifications≈ 140 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • unread_only · boolean · optionnel

  Exemple d'appel

  {"name": "get_notifications", "arguments": {"limit": 1, "unread_only": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_relationships≈ 228 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • listing · string · requis
    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.

  Exemple d'appel

  {"name": "get_relationships", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_watchlist≈ 90 tokens

  The companies the user watches on FirmLedger, newest first.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_watchlist", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_ad_packages≈ 144 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_ad_packages", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_api_keys≈ 112 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_api_keys", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_categories≈ 108 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_categories", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_countries≈ 104 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_countries", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_jobs≈ 313 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · ? · optionnel
    limit. Integer or numeric string, clamped to 1–25.
  • query · string · optionnel
    Optional keyword in the job title or description.
  • offset · ? · optionnel
    offset. Integer or numeric string, clamped to 0–10000.
  • company · string · optionnel
    Optional company (slug, exact name, FirmLedger ID or profile URL).
  • location · string · optionnel
    Optional location, e.g. "Nairobi" or "Kenya" or "Remote".

  Exemple d'appel

  {"name": "list_jobs", "arguments": {"limit": "texte", "query": "texte", "offset": "texte", "company": "texte", "location": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_leads≈ 235 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • box · string · optionnel · received | archived | sent
  • page · integer · optionnel
  • limit · integer · optionnel
  • status · string · optionnel · new | contacted | qualified | won | lost
  • listing · string · optionnel
    Optional: only leads for this listing of the user's.

  Exemple d'appel

  {"name": "list_leads", "arguments": {"box": "received", "page": 1, "limit": 1, "status": "new", "listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_my_tickets≈ 132 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • ticket · string · optionnel
    Optional ticket reference, e.g. "TK-1A2B3C".

  Exemple d'appel

  {"name": "list_my_tickets", "arguments": {"ticket": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_plans≈ 129 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_plans", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_webhooks≈ 179 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • webhook_id · integer · optionnel
    Optional: one destination, with its recent deliveries.

  Exemple d'appel

  {"name": "list_webhooks", "arguments": {"limit": 1, "webhook_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• manage_api_keys≈ 394 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • label · string · optionnel
    create: a name for the key.
  • action · string · requis · create | revoke | update_scopes
  • key_id · integer · optionnel
    revoke/update_scopes: the key id from list_api_keys.
  • scopes · array · optionnel
    Scope ids. Required for update_scopes; create defaults to the standard scopes.
  • key_prefix · string · optionnel
    Optional alternative to key_id.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "manage_api_keys", "arguments": {"action": "create"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• manage_job≈ 324 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • title · string · optionnel
  • action · string · requis · edit | close | remove | delete
  • job_id · integer · requis
  • location · string · optionnel
  • apply_url · string · optionnel
  • role_type · string · optionnel · Full-time | Part-time | Contract | Internship | Remote
  • description · string · optionnel
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "manage_job", "arguments": {"action": "edit", "job_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• manage_lead≈ 254 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • action · string · requis · archive | unarchive | delete
  • lead_id · integer · requis
    The lead id from list_leads.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "manage_lead", "arguments": {"action": "archive", "lead_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• manage_webhooks≈ 410 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • url · string · optionnel
    create/update: the receiver URL (https in production).
  • label · string · optionnel
  • action · string · requis · create | update | pause | resume | rotate_secret | test | retry_delivery | delete
  • events · array · optionnel
    create/update: event types to subscribe to.
  • categories · array · optionnel
  • webhook_id · integer · optionnel
    Required for every action except create.
  • delivery_id · integer · optionnel
    retry_delivery: which delivery to retry.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "manage_webhooks", "arguments": {"action": "create"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• mark_notifications_read≈ 198 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • all · boolean · optionnel
  • notification_id · integer · optionnel
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "mark_notifications_read", "arguments": {"all": true, "notification_id": 1, "confirmation_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• post_job≈ 368 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • title · string · requis
  • listing · string · requis
    One of the user's own listings.
  • location · string · requis
    City, or "Remote".
  • apply_url · string · requis
    Full https:// link to the job post or careers page.
  • role_type · string · optionnel · Full-time | Part-time | Contract | Internship | Remote
  • description · string · requis
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "post_job", "arguments": {"title": "texte", "listing": "texte", "location": "texte", "apply_url": "texte", "description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• prepare_advertising≈ 258 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • listing · string · requis
    One of the user's own approved listings (see get_my_listings or list_ad_packages).
  • package · string · requis
    The package id from list_ad_packages (or its exact name).

  Exemple d'appel

  {"name": "prepare_advertising", "arguments": {"listing": "texte", "package": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• prepare_listing_claim≈ 229 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • method · string · optionnel · dns | meta | badge
  • listing · string · requis
    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.

  Exemple d'appel

  {"name": "prepare_listing_claim", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• prepare_listing_submission≈ 297 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • city · string · optionnel
    Optional city.
  • name · string · requis
    Company name.
  • country · string · optionnel
    Optional country.
  • website · string · optionnel
    Company website, e.g. "example.co.ke".
  • category · string · optionnel
    Optional category.

  Exemple d'appel

  {"name": "prepare_listing_submission", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• prepare_upgrade≈ 253 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • plan · string · optionnel
    The plan id from list_plans (or its exact name).
  • promo_code · string · optionnel
    Optional promo code the user gave you.

  Exemple d'appel

  {"name": "prepare_upgrade", "arguments": {"plan": "texte", "promo_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• refresh_listing_news≈ 237 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • listing · string · requis
    One of the user's own approved listings.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "refresh_listing_news", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• refresh_listing_scores≈ 231 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • listing · string · requis
    One of the user's own listings.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "refresh_listing_scores", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• refresh_listing_tech≈ 229 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • listing · string · requis
    One of the user's own listings.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "refresh_listing_tech", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reply_to_lead≈ 252 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • lead_id · integer · requis
  • message · string · requis
    The reply text, written or approved by the user.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "reply_to_lead", "arguments": {"lead_id": 1, "message": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reply_to_ticket≈ 285 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • ticket · string · requis
    The ticket reference (e.g. TK-1A2B3C) or its id, from list_my_tickets.
  • message · string · requis
    The reply text, written or approved by the user.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "reply_to_ticket", "arguments": {"ticket": "texte", "message": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• request_authentication≈ 308 tokens

  Connect this assistant to the member's own FirmLedger account by sign-in (OAuth), or renew or replace that connection. Call it when the member says "connect me to my account", "sign me in", or asks to switch accounts. The assistant opens FirmLedger in the browser, the member approves there, and no password or key passes through the chat. mode "connect" (the default) starts sign-in when the connection needs it. mode "reauthenticate" ends the current connection so the member can choose the account again. mode "refresh" renews a sign-in token that is about to expire, and the assistant should then retry.

  Paramètres, retour & exemple (1)

  Paramètres

  • mode · string · optionnel · connect | reauthenticate | refresh
    connect (default): sign in if needed. reauthenticate: end this connection so the member can choose the account again. refresh: renew a token that is about to expire.

  Exemple d'appel

  {"name": "request_authentication", "arguments": {"mode": "connect"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• request_listing_removal≈ 265 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • reason · string · requis
    Why it should be removed (20+ characters).
  • listing · string · requis
    A listing the user owns or submitted.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "request_listing_removal", "arguments": {"reason": "texte", "listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• revoke_connection≈ 180 tokens

  Disconnect this assistant from the member's FirmLedger account. The sign-in is revoked on FirmLedger's side at once, and every token it issued stops working. Call it when the member asks to remove, sign out or disconnect their account. It cannot erase the token stored in the member's assistant app, so tell the member to remove the FirmLedger connector there as well.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "revoke_connection", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_listings≈ 476 tokens

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

  Paramètres, retour & exemple (8)

  Paramètres

  • city · string · optionnel
    City or region, e.g. "Nairobi".
  • type · string · optionnel · company | startup | agency | organization | product | service | publisher
    Entity type.
  • limit · ? · optionnel
    Results per page (1-25).. Integer or numeric string, clamped to 1–25.
  • query · string · optionnel
    Company name or keyword (matched against name, tagline, description, tags and city).
  • offset · ? · optionnel
    Results to skip, for paging (use next_offset).. Integer or numeric string, clamped to 0–10000.
  • country · string · optionnel
    Country name, e.g. "Kenya".
  • category · string · optionnel
    Category name, e.g. "Fintech". Call list_categories for valid names.
  • verified_only · ? · optionnel
    Only ownership-verified records (boolean or the string true/false).

  Exemple d'appel

  {"name": "search_listings", "arguments": {"city": "texte", "type": "company", "limit": "texte", "query": "texte", "offset": "texte", "country": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_lead_status≈ 217 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • status · string · requis · new | contacted | qualified | won | lost
  • lead_id · integer · requis
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "set_lead_status", "arguments": {"status": "new", "lead_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• start_lead≈ 372 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • name · string · optionnel
    Optional sender name; defaults to the member profile name.
  • phone · string · optionnel
  • listing · string · requis
    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.
  • message · string · requis
  • looking_for · string · optionnel
    Optional short subject or what the member needs.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "start_lead", "arguments": {"listing": "texte", "message": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_my_listing≈ 591 tokens

  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.

  Paramètres, retour & exemple (17)

  Paramètres

  • city · string · optionnel
  • name · string · optionnel
  • size · string · optionnel
  • tags · string · optionnel
  • email · string · optionnel
  • phone · string · optionnel
  • region · string · optionnel
  • address · string · optionnel
  • country · string · optionnel
  • founded · string · optionnel
  • listing · string · requis
    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.
  • socials · ? · optionnel
    Social profile links keyed by network; use an empty object to clear. A JSON object string is also accepted.
  • tagline · string · optionnel
  • website · string · optionnel
  • logo_url · string · optionnel
  • description · string · optionnel
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "update_my_listing", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• watchlist_add≈ 247 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • listing · string · requis
    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.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "watchlist_add", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• watchlist_remove≈ 238 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • listing · string · requis
    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.
  • confirmation_token · string · optionnel
    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.

  Exemple d'appel

  {"name": "watchlist_remove", "arguments": {"listing": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.firmledger.co.ke/mcp