AppBoard.pro product discovery
REMOTE · API.APPBOARD.PRO · SCANNED SEP 28
Search community-ranked software products: trending launches, details, and alternatives to a tool.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 916 tokens (~130/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the AppBoard.pro product discovery MCP server?
AppBoard.pro product discovery is a hosted endpoint at https://api.appboard.pro/api/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 · api.appboard.pro
claude mcp add --transport http pro-appboard-appboard 'https://api.appboard.pro/api/mcp'
{
"mcpServers": {
"pro-appboard-appboard": {
"url": "https://api.appboard.pro/api/mcp"
}
}
} {
"servers": {
"pro-appboard-appboard": {
"type": "http",
"url": "https://api.appboard.pro/api/mcp"
}
}
} [mcp_servers.pro-appboard-appboard] url = "https://api.appboard.pro/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pro-appboard-appboard": {
"type": "remote",
"url": "https://api.appboard.pro/api/mcp",
"enabled": true
}
}
} openclaw mcp add pro-appboard-appboard --url 'https://api.appboard.pro/api/mcp' --transport streamable-http
mcp_servers:
pro-appboard-appboard:
url: "https://api.appboard.pro/api/mcp" {
"McpServers": {
"pro-appboard-appboard": {
"Transport": "http",
"Url": "https://api.appboard.pro/api/mcp"
}
}
} assistant mcp add pro-appboard-appboard -t streamable-http -u 'https://api.appboard.pro/api/mcp'
{
"mcpServers": {
"pro-appboard-appboard": {
"type": "http",
"url": "https://api.appboard.pro/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 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.
- 16 Sept 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.
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 28 Sept 2026 · Probed https://api.appboard.pro/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=appboard.pro | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | cc42bc95552476400e378f7cd494e0ec |
| SANs: appboard.pro, *.appboard.pro | ||||||
| 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 api.appboard.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 42154 | 8 | Verified |
| appboard.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.appboard.pro/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.appboard.pro/api/mcp | Inconclusive | 405 |
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 →
appboard_alternatives_to ~140
Find products offered as alternatives to a tool the user ALREADY USES — "what can I use instead of Notion / Product Hunt / Zapier". Pass the tool's target slug. This differs from appboard_find_alternatives, which starts from a product listed on AppBoard; use this one when the user names the tool they want to replace. Call appboard_list_alternative_targets when unsure which slug a tool has.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | the tool the user wants to replace, as an AppBoard target slug from appboard_list_alternative_targets, e.g. 'product-hunt' or 'notion' |
No output schema declared.
No examples provided.
appboard_browse_taxonomy ~88
List the controlled vocabulary for a dimension — categories, use cases, platforms, audiences or pricing models. Call this to discover the exact filter values appboard_find_products accepts, and to answer "what categories exist". Each term carries the appboardUrl of its browse page.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | which vocabulary to list: category, use_case, platform, audience or pricing |
No output schema declared.
No examples provided.
appboard_find_alternatives ~118
Find alternatives and competitors to a specific product. Use this for "what's a good alternative to X" or "what else is like X". Alternatives that are themselves on AppBoard include a slug you can pass to appboard_product_details and an appboardUrl. When the tool being replaced has an AppBoard collection, alternativesPage is the URL of that "alternatives to X" page — share it with the user.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | the product's AppBoard slug, as returned by appboard_find_products |
No output schema declared.
No examples provided.
appboard_find_products ~275
Search AppBoard for software products by need, category, use case, platform, audience or pricing model. Use this whenever the user asks what tool to use for a job ("a free email API", "note-taking apps for teams"). Results are ranked by real community engagement, not by advertising. Filter values are the names returned by appboard_browse_taxonomy — an unknown name is an error, so list the vocabulary first if you are unsure. Each product carries an appboardUrl, and each of its categories, use cases and platforms carries the appboardUrl of its browse page.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | comma-separated target-audience names, e.g. 'developers' |
| category | string | – | comma-separated category names from appboard_browse_taxonomy, e.g. 'ai,developer-tools' |
| limit | integer | – | how many products to return (1-50, default 10) |
| platform | string | – | comma-separated platform names, e.g. 'web,ios,api' |
| pricing | string | – | comma-separated pricing-model names, e.g. 'free,freemium' |
| query | string | – | free-text terms to match against product names and taglines |
| use_case | string | – | comma-separated use-case names from appboard_browse_taxonomy |
No output schema declared.
No examples provided.
appboard_list_alternative_targets ~81
List the tools AppBoard has alternatives for, most-covered first, with the slug to pass to appboard_alternatives_to. Use it to resolve a tool name to a slug, or to answer "what tools do you cover alternatives for".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | how many targets to return (1-50, default 10) |
No output schema declared.
No examples provided.
appboard_product_details ~111
Get everything AppBoard knows about one product: what it does, its pricing model, platforms, use cases, target audiences, community metrics, any discount code, and its alternatives. Use after appboard_find_products when the user asks about a specific product. Taxonomy terms link to their browse pages; an alternative that has its own AppBoard collection carries alternativesPage — the URL to open for it.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | the product's AppBoard slug, as returned by appboard_find_products |
No output schema declared.
No examples provided.
appboard_trending ~103
List the products gaining the most community momentum in a time window. Use this for "what's new/hot/trending" questions. Ranked by AppBoard's Points-Based Score, which weights recent upvotes, comments, follows and saves by recency.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | how many products to return (1-50, default 10) |
| period | string | – | time window: today, yesterday, week, month or all (default week) |
No output schema declared.
No examples provided.
What is the AppBoard.pro product discovery MCP server?
AppBoard.pro product discovery is an MCP server listed in the public MCP registry as pro.appboard/appboard. Search community-ranked software products: trending launches, details, and alternatives to a tool. This page covers its hosted endpoint (https://api.appboard.pro/api/mcp).
Is the AppBoard.pro product discovery MCP server safe to use?
AppBoard.pro product discovery scores 70 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 AppBoard.pro product discovery MCP server expose?
AppBoard.pro product discovery exposes 7 tools: appboard_alternatives_to, appboard_browse_taxonomy, appboard_find_alternatives, appboard_find_products, appboard_list_alternative_targets, and 2 more. Their descriptions and schemas cost roughly 916 tokens of context every time the server is loaded.
Does the AppBoard.pro product discovery MCP server require authentication?
No. We connected to AppBoard.pro product discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AppBoard.pro product discovery MCP server still maintained?
AppBoard.pro product discovery is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.