Foundingbird
REMOTE · PORTAL.FOUNDINGBIRD.COM
Incorporate and manage your Malaysian Sdn Bhd from AI: SSM docs, cosec requests, deadlines.
Available components
Last scanned (20 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
Recent critical change
Authorization (10 Nov 2026). See the changelog before you install this server.
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 Security63
- 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 (cancel_application). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4615 tokens (~139/item across 33 items; 30 tools + 3 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% 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
- We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 +28
- Authorization: pass → fail ▼ critical
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Capabilities: pass functional
- First check of Tool coverage: 94 functional
- First check of Schema quality: good functional
- 9 Nov 26 39
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 21 Nov 2026 · Probed https://portal.foundingbird.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foundingbird.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1a6c0d982ab99f950e888698c32a13d3 |
| SANs: foundingbird.com, *.foundingbird.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of portal.foundingbird.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| foundingbird.com. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://portal.foundingbird.com/mcp | Verified | 200 | |
| http (plaintext) | http://portal.foundingbird.com/mcp | HTTPS enforced | 301 | https://portal.foundingbird.com/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 →
cancel_application Cancel an application ~64
Cancel one of the signed-in customer's draft applications that was never submitted, freeing its company name. It can't be resumed afterwards. Only call it after the customer explicitly confirms.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
No output schema declared.
No examples provided.
check_company_name Check a company name ~111
Whether a proposed Sdn Bhd name is already in use on this firm's platform (exact match only), what SSM's naming rules refuse in it (naming_problems: the name must change), and which words need an authority's approval (approval_warnings: allowed, the firm follows up). It is not an SSM name search: SSM confirms availability when the incorporation is filed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The proposed name. A trailing "Sdn. Bhd." is ignored. |
No output schema declared.
No examples provided.
choose_package Choose a package ~115
Choose the items on one checkout step of a submitted application, replacing that step's previous choice. Item ids come from get_checkout; an empty list clears an optional step. Returns the updated cart.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
| interval | string | – | Billing interval, for steps that offer a choice. |
| item_ids | array | yes | Item ids from get_checkout for this step. |
| step | string | yes | The step's slug from get_checkout. |
No output schema declared.
No examples provided.
create_billing_link Get a link to an invoice or statement ~112
A link the signed-in customer clicks to sign in on the firm's website at one of their company's billing pages: "billing" to pay what's outstanding, "invoice" for one invoice from list_invoices (give its invoice_id), "statement" to download the statement of accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
| invoice_id | string | – | The invoice's id (inv_…), from list_invoices. |
| purpose | string | yes | – |
No output schema declared.
No examples provided.
create_company_link Get a link to a company page on the website ~108
A link the signed-in customer clicks to act on one of their companies on the firm's website: "signing" to sign documents, "verification" for identity verification, "annual_return" to approve the annual return, "invoices" to see and pay invoices. get_company's needs_you says which apply. Signing, payment and approvals never happen in chat.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
| purpose | string | yes | – |
No output schema declared.
No examples provided.
create_document_link Get a link to open a document ~173
A link the signed-in customer clicks to open one of their company's documents on the firm's website, after signing them in: a file from find_company_documents (folder_id and file_id), a letter from list_letters (letter_id), or a signing request from list_signing_requests (signing_request_id). Give one of the three. The document never comes into the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
| file_id | string | – | The file's id, from find_company_documents. |
| folder_id | string | – | A folder's id, from find_company_documents. |
| letter_id | string | – | The letter's id, from list_letters. |
| signing_request_id | string | – | The signing request's id, from list_signing_requests. |
No output schema declared.
No examples provided.
create_handoff_link Get a link to continue on the website ~104
A link the signed-in customer clicks to continue on the firm's website, already signed in: "payment" to pay (after choosing packages), "verification" for identity verification, "signing" to sign documents, "documents" to upload a switch-in's documents. Payment, ID documents and signatures never go through chat.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
| purpose | string | yes | – |
No output schema declared.
No examples provided.
describe_flow Describe an application ~117
The steps of one service's application, in order, each with the JSON Schema of the fields the customer fills in, and the stages after submission (payment, identity verification, signing, filing). Use it to know what to ask the customer.
| Name | Type | Req | Description |
|---|---|---|---|
| flow | string | yes | The service: "incorporation-sdn-bhd" registers a new Sdn Bhd; "switch-in-sdn-bhd" moves an existing Sdn Bhd to this firm as its company secretary. get_firm_overview lists what this firm offers. |
No output schema declared.
No examples provided.
estimate_quote Estimate a quote ~212
Price a selection of packages and add-ons for one service: one-time and recurring totals, tax and the grand total. Selections map a list_packages step slug to the item ids chosen on that step. Reports required steps left without a choice.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | object | – | Answers to the conditions some package steps depend on, as list_packages reports them, e.g. {"requires_virtual_office": true} when the customer has no business address of their own. |
| flow | string | yes | The service: "incorporation-sdn-bhd" registers a new Sdn Bhd; "switch-in-sdn-bhd" moves an existing Sdn Bhd to this firm as its company secretary. get_firm_overview lists what this firm offers. |
| interval | string | – | Billing interval for steps that offer a choice. Defaults to each step's own default. |
| selections | object | yes | Step slug → item ids from list_packages, e.g. {"package": ["pri_abc123"]}. |
No output schema declared.
No examples provided.
explain_deadline Explain a company deadline ~108
Explains one of a company's compliance deadlines, by the deadline_key get_company gives each: what it is, which authority it's for, whose job it is, what the customer has to do, the penalty for missing it, and for an annual return or an ownership confirmation, who has and hasn't done their part yet.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
| deadline_key | string | yes | The deadline's key, from get_company. |
No output schema declared.
No examples provided.
find_company_documents Find a company's documents ~416
The documents the signed-in customer can open for one of their companies, from the firm's document store: with no query or folder_id, its folders (Statutory Forms, Minutes Book, Correspondence, Customer Letters); with folder_id, what's in that folder; with query, files whose name holds every word, or, when no name matches, files whose text does (matched_by "contents"). Names, folders and dates only, never what a file says. Search by the name the file likely has in Malaysia: Certificate of incorporation: "S 17 - Certificate of Incorporation" if the company applied for one (s.17), else "S 15 - Notice of Registration", which is conclusive evidence of registration (s.19); "Form 9" for a company incorporated before 2017. Superform (registration application): "S 14 - Superform". Constitution: "Constitution"; "Memorandum and Articles" or "M&A" for an older company. Return of allotment of shares: "S 78"; "Form 24" before 2017. Change of directors or secretary: "S 58"; "Form 49" before 2017. Change of registered address: "S 46"; "Form 44" before 2017. Annual return: "S 68" or "Annual Return"; "Form 50" before 2017. Beneficial ownership (e-BOS): "S 60B" or "e-BOS". Try the likeliest name first, then the next; if nothing matches, list Statutory Forms and choose by name. create_document_link gives the customer a link to open one.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
| folder_id | string | – | A folder's id, from find_company_documents. |
| query | string | – | Words in the file's name, e.g. "superform" or "notice registration". |
No output schema declared.
No examples provided.
get_application Get an application ~62
One of the signed-in customer's applications: status, each step's saved answers and whether the step is complete or what to fix, and what to do next.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
No output schema declared.
No examples provided.
get_business_classification Get the business classification draft ~81
The drafted business description, company-name explanation and MSIC codes for an incorporation, for the customer to review before saving the business_classification step. The draft is made in the background after company_details is saved; poll while its status is pending.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
No output schema declared.
No examples provided.
get_checkout Get an application's packages ~107
The packages and add-ons for one of the signed-in customer's applications, as its answers make them apply: item ids and prices per step, what's already chosen, required steps without a choice, and the total so far. Items carry the firm's own sales wording: a badge on the option it recommends, a tagline, what's included (features) and fine print such as per-change fees.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
No output schema declared.
No examples provided.
get_company Get a company's details and deadlines ~125
One of the signed-in customer's companies: its details, what needs them (needs_you, each with the create_company_link purpose that opens it), and its compliance deadlines: attention (overdue, waiting on them, or due soon) and upcoming. owner says whose job each deadline is: "cosec" (the firm), "you" (the customer), or another adviser such as "tax_agent" or "auditor". explain_deadline explains one by its deadline_key.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
No output schema declared.
No examples provided.
get_company_particulars Get a company's particulars ~107
One of the signed-in customer's companies as it stands on its register: legal and former name, entity type, registration numbers, incorporation date, registered and business address, nature of business (MSIC codes), financial year end, whether it has a constitution, its share capital by class, and its company secretary, auditor and tax agent. For directors and shareholders use get_company_registers.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
No output schema declared.
No examples provided.
get_company_registers Get a company's directors and shareholders ~112
The register of directors and the register of members of one of the signed-in customer's companies: each director's name, nationality, type and appointment date (and former directors), and each shareholder's name, nationality (a company's country of incorporation), whether it's an individual or a company, and its shares by class with its percentage of the company. you marks the customer. No identity numbers or contact details are available here.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
No output schema declared.
No examples provided.
get_firm_overview Get firm overview ~61
What this company secretarial firm offers: the services a customer can start here (with the flow name the other tools take), whether it provides a virtual office address and a nominee director, its policy links and how the process works. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_status Get an application's status ~102
Where one of the signed-in customer's applications stands after submission: each step to a registered company (or, for a switch-in, to being live with the firm), which is done and when, whose move the current one is, who still has to verify their identity or sign, and what the customer needs to do on the website (create_handoff_link).
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
No output schema declared.
No examples provided.
list_applications List my applications ~37
The signed-in customer's applications with this firm, newest first: id, service, status and company name. Cancelled applications are left out.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_companies List my companies ~74
The companies the signed-in customer is part of with this firm (as director, shareholder, authorised user, …): id, legal name, registration number, status, their roles, and what each needs from them (needs_you). status "left" means the company no longer uses this firm. get_company has the deadlines.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_invoices List a company's invoices ~135
The invoices the firm has sent one of the signed-in customer's companies, newest first: number, what it was for, dates, total, what's still owed and status ("paid", "open", "overdue", "uncollectible"), with the outstanding total. by_bank_transfer means the customer pays it by bank transfer, not online. create_billing_link opens an invoice, the statement of accounts or the Billing page to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
| status | string | – | "outstanding" for only what's still owed. Defaults to all. |
No output schema declared.
No examples provided.
list_letters List a company's letters ~125
The letters the firm has received for one of the signed-in customer's companies at its registered office, newest first: title, sender and the date it arrived, and new: true for one that came since the customer last opened their Letterbox. You only see these details, never the letter itself; don't guess what it says. create_document_link with letter_id opens the scan on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
| since | string | – | Only letters that arrived on or after this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
list_packages List packages and prices ~162
The packages and add-ons for one service, step by step, with prices in the firm's currency and the item ids estimate_quote takes. Some steps only apply under a condition (listed under conditions); pass flags to see the steps as that customer would.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | object | – | Answers to the conditions some package steps depend on, as list_packages reports them, e.g. {"requires_virtual_office": true} when the customer has no business address of their own. |
| flow | string | yes | The service: "incorporation-sdn-bhd" registers a new Sdn Bhd; "switch-in-sdn-bhd" moves an existing Sdn Bhd to this firm as its company secretary. get_firm_overview lists what this firm offers. |
No output schema declared.
No examples provided.
list_signing_requests List a company's signing requests ~124
The e-signing requests at one of the signed-in customer's companies that they're on, newest first: name, status ("in_progress", "completed", "declined", "expired", "voided"), when it was sent, its documents, the customer's own part (sign or view) and where it stands, and each signer by name with whether they've signed. create_document_link with signing_request_id opens one on the website, to sign it or download the signed documents.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company's id (com_…), from list_companies. |
No output schema declared.
No examples provided.
regenerate_business_classification Redraft the business classification ~71
Draft an incorporation's business description, name explanation and MSIC codes again, e.g. after the first draft failed or the customer wants fresh suggestions. Poll get_business_classification for the result.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
No output schema declared.
No examples provided.
search_msic_codes Search MSIC codes ~121
Find five-digit MSIC 2008 business activity codes by what the business does (e.g. "software development", "online shop", "cafe") or by the first digits of a code (e.g. "620"). Each match says what the code includes, officially. Once company_details is saved, get_business_classification suggests codes drafted from the customer's own description; use this to look up alternatives. The business classification step takes up to three codes.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Words describing the activity, or the start of a code. |
No output schema declared.
No examples provided.
start_application Start an application ~102
Start the signed-in customer's application for a service, or resume their open draft for it. Returns the application id and its steps; fill them in with update_application_step.
| Name | Type | Req | Description |
|---|---|---|---|
| flow | string | yes | The service: "incorporation-sdn-bhd" registers a new Sdn Bhd; "switch-in-sdn-bhd" moves an existing Sdn Bhd to this firm as its company secretary. get_firm_overview lists what this firm offers. |
No output schema declared.
No examples provided.
submit_application Submit an application ~121
Submit the signed-in customer's finished application to the firm. Only call it after showing the customer the firm's terms and policies (get_firm_overview links them) and the declaration that the application is true and complete, and after they explicitly agree. Submitting again after a change sends the update.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
| terms_accepted | boolean | yes | The customer has read the firm's terms and policies and declares the application true and complete. Only true after they explicitly agree. |
No output schema declared.
No examples provided.
update_application_step Fill in an application step ~122
Save the customer's answers for one step of their application. Fields follow the step's JSON Schema from describe_flow; fields left out keep their saved values. Returns what to fix per field when an answer is refused, in which case nothing was saved.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application's id (obs_…), from list_applications or start_application. |
| fields | object | yes | The step's fields, as its JSON Schema in describe_flow describes them. |
| step | string | yes | The step's key from describe_flow, e.g. "company_details". |
No output schema declared.
No examples provided.
How do I install the Foundingbird MCP server?
Foundingbird is a hosted endpoint at https://portal.foundingbird.com/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 · portal.foundingbird.com
claude mcp add --transport http com-foundingbird-mcp 'https://portal.foundingbird.com/mcp'
What is the Foundingbird MCP server?
Foundingbird is an MCP server listed in the public MCP registry as com.foundingbird/mcp. Incorporate and manage your Malaysian Sdn Bhd from AI: SSM docs, cosec requests, deadlines. This page covers its hosted endpoint (https://portal.foundingbird.com/mcp).
Is the Foundingbird MCP server safe to use?
Foundingbird scores 73 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 Foundingbird MCP server expose?
Foundingbird exposes 30 tools: get_firm_overview, describe_flow, list_packages, estimate_quote, check_company_name, and 25 more. Their descriptions and schemas cost roughly 3,591 tokens of context every time the server is loaded.
Does the Foundingbird MCP server require authentication?
No. We connected to Foundingbird without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Foundingbird MCP server still maintained?
Foundingbird is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Foundingbird MCP server?
VerifyMCP ran 14 checks on Foundingbird, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.