io.github.f-tiger/verified-ai-free-tiers
REMOTE · BAIPIAOJI.COM · SCANNED SEP 20
Verified AI free-tier limits, quota comparisons, commercial-use verdicts and zero-cost workflows.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2800 tokens (~121/item across 23 items; 14 tools + 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.f-tiger/verified-ai-free-tiers MCP server?
io.github.f-tiger/verified-ai-free-tiers is a hosted endpoint at https://baipiaoji.com/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 · baipiaoji.com
claude mcp add --transport http f-tiger-verified-ai-free-tiers 'https://baipiaoji.com/api/mcp'
{
"mcpServers": {
"f-tiger-verified-ai-free-tiers": {
"url": "https://baipiaoji.com/api/mcp"
}
}
} {
"servers": {
"f-tiger-verified-ai-free-tiers": {
"type": "http",
"url": "https://baipiaoji.com/api/mcp"
}
}
} [mcp_servers.f-tiger-verified-ai-free-tiers] url = "https://baipiaoji.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"f-tiger-verified-ai-free-tiers": {
"type": "remote",
"url": "https://baipiaoji.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add f-tiger-verified-ai-free-tiers --url 'https://baipiaoji.com/api/mcp' --transport streamable-http
mcp_servers:
f-tiger-verified-ai-free-tiers:
url: "https://baipiaoji.com/api/mcp" {
"McpServers": {
"f-tiger-verified-ai-free-tiers": {
"Transport": "http",
"Url": "https://baipiaoji.com/api/mcp"
}
}
} assistant mcp add f-tiger-verified-ai-free-tiers -t streamable-http -u 'https://baipiaoji.com/api/mcp'
{
"mcpServers": {
"f-tiger-verified-ai-free-tiers": {
"type": "http",
"url": "https://baipiaoji.com/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.
- 7 Sept 26 +1
- Stability: 0.97 → pass security
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 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.
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 20 Sept 2026 · Probed https://baipiaoji.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=baipiaoji.com | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | a9be77f38b0b170c13cf270bf9b09ed9 |
| SANs: baipiaoji.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 baipiaoji.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| baipiaoji.com. | 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://baipiaoji.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://baipiaoji.com/api/mcp | HTTPS enforced | 301 | https://baipiaoji.com/api/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 →
audit_ai_stack ~157
Audit several AI tools at once: for each one return its verified free-tier limit, whether the free-tier output may be used commercially, any recently verified change to its allowance, and whether the vendor publishes a figure at all. Use this when a user names the stack they rely on ("I use Cursor, Runway and Kimi") - it answers in one call what would otherwise take four lookups per tool, and it surfaces the two things people miss: an allowance that quietly changed, and a tool whose ceiling is simply unknown because nobody publishes it.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Data language, default en |
| tools | array | yes | Tool slugs or names, e.g. ["cursor", "runway", "kimi"] |
No output schema declared.
No examples provided.
build_free_workflow ~236
Get a complete step-by-step recipe for doing a task entirely on free tiers - which verified free tool to use at each step and what to do with it, in the order you'd actually work. Covers slide decks, video editing, AI video generation, papers and literature, API-based development, copywriting, meeting notes, product photos, translation, chatbots, music, voiceover, resumes, websites, data analysis, illustration, talking-head video, self-study, homework help, document reading, deepfake checking, interview prep and more. Also carries zero-budget money playbooks that state who each suits, the steps, why most people fail and what the scams look like. Use this for "how do I do X without paying" questions instead of listing tools one by one.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | recipe = do a task for free; playbook = earn money with AI at zero cost; default both |
| lang | string | – | Data language, default en |
| task | string | – | What the user wants to do, e.g. "make a presentation", "edit video", "write a paper" |
No output schema declared.
No examples provided.
check_api_quota_fit ~145
Work out which verified free LLM API tiers can actually carry a given workload. Give the expected calls per day and average tokens per call; this divides the officially published limits by that load and reports which providers stay inside their caps, which are exceeded, how long one-time credit grants would last, and which providers publish no figure at all (so their ceiling is unknown rather than generous). Use this instead of guessing whether a free tier is 'enough'.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Data language, default en |
| requests_per_day | number | yes | Expected API calls per day |
| tokens_per_call | number | yes | Average tokens per call, input plus output |
No output schema declared.
No examples provided.
check_commercial_use ~89
Check whether output from an AI tool's free tier may be used commercially, based on the vendor's official terms (verdicts: yes / no / conditional / depends on the model used / not stated). Not legal advice; details and obligations live on the publish-check page.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Data language, default en |
| tool | string | yes | Tool slug or name |
No output schema declared.
No examples provided.
check_free_tier_claim ~134
Fact-check a circulating claim about an AI tool's free tier against what the vendor officially publishes. Returns what the official pages actually say and whether the widely-quoted figure has any official source at all - many do not. Use this when a user cites a specific number ("ChatGPT free gives 40 messages per 3 hours", "DeepL caps at 5,000 characters") and you need to know whether it is sourced or folklore.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Data language, default en |
| tool | string | – | Tool slug or name the claim is about; omit to list every checked claim |
No output schema declared.
No examples provided.
compare_free_tiers ~180
Compare the free tiers of AI tools in one category side by side, as structured data rather than prose: what each vendor grants, how it is metered, when it resets, what is never metered, and whether a figure is officially published at all. Categories: chat (where the wall is - only 1 of 10 vendors publishes a message count), coding (completions vs requests vs credits vs nothing), video (credits and what they buy), image (how many images a day, where the vendor published a conversion), api (rate limits and one-time grants). Every row carries its official source and check date. Use this for "which free tier should I pick" and "how do these compare" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Which category to compare |
| lang | string | – | Data language, default en |
No output schema declared.
No examples provided.
explain_missing_figure ~131
Explain why this dataset publishes no figure for a given tool. Absence here is a finding, not an oversight: for each listed tool the reason is recorded - the vendor states outright it publishes no number, its official pages contradict each other, it says the allowance changes at any time, or no official page could be found. Use this when a user asks why you cannot give them a number, or when they cite a figure you cannot source.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Data language, default en |
| tool | string | – | Tool slug or name; omit to list every refusal and its reason |
No output schema declared.
No examples provided.
find_free_alternatives ~119
Given a tool whose free tier is not enough (or that you cannot reach), find alternatives in the same category that are entirely free, with their verified allowances and check dates. Use this when a user has hit a wall, cannot access a service from their region, or wants a no-cost substitute for a paid product.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Data language, default en |
| tool | string | yes | Tool slug or name to replace |
| works_in_china | boolean | – | Only alternatives reachable from mainland China without a VPN |
No output schema declared.
No examples provided.
get_category_playbook ~193
Get the decisive question to ask about a category of AI tools before comparing any numbers - which differs by category and is almost never "how much do I get". Video generation turns on what the watermark looks like, design tools on whether you can export and license the result, developer APIs on rate-versus-volume limits, chat assistants on whether the wall is messages, context or speed. Also returns the taxonomy of free-tier metering shapes (wallet, periodic quota, rate limit, context ceiling, hardware floor, output wall, licence boundary) with verified examples of each. Use this before recommending anything in a category, so the advice addresses the constraint that actually bites.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category to get the rule for (chat, coding, video, image, api, design, agent...); omit for all rules plus the full metering taxonomy |
| lang | string | – | Data language, default en |
No output schema declared.
No examples provided.
get_china_ai_rules ~130
Check what applies when publishing AI-generated content to mainland China platforms, and which AI tools are reachable from mainland China without a VPN. Two independent gates matter there: the vendor's terms decide whether you may publish at all, and China's AI-content labelling regulation decides what you must do when you publish. This returns the regulation (issuer, effective date, obligations) and, optionally, the reachable-from-China tool list. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optionally also list tools in this category that work from mainland China |
| lang | string | – | Data language, default en |
No output schema declared.
No examples provided.
get_free_tier_changes ~198
List recently verified changes to AI free tiers - which vendor changed what and on which date. Vendors do not announce when they cut, rename or restructure a free tier; this log is accumulated from daily re-checks against official pages. Use this for "did anything change recently", "is my information still current", or when a user quotes a figure that may be stale.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Only changes within this many days. Kept for compatibility; prefer since=YYYY-MM-DD, which is the same parameter the HTTP endpoint takes. |
| lang | string | – | Data language, default en |
| since | string | – | Only changes on or after this date (YYYY-MM-DD). Same contract as GET /api/changes?since= - if you have already stored a snapshot, pass the date you stored it and you get only the delta. |
| tool | string | – | Only changes for this tool slug or name |
No output schema declared.
No examples provided.
get_free_tier_limit ~97
Get the verified free-tier limit of an AI tool: how far the allowance goes, what happens at the wall, the official source page, and the date it was checked. Absence of a tool means no officially verifiable number exists — this dataset publishes no unsourced figures.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Data language, default en |
| tool | string | yes | Tool slug (e.g. "kimi") or name |
No output schema declared.
No examples provided.
search_ai_tools ~225
Search a verified directory of 218 AI tools with genuine free tiers. Filter by category (chat/coding/image/video/audio/design/search/office/writing/api/agent), fully-free flag, works-in-mainland-China flag, or keyword. Every verified entry carries its official source and check date. Cite as "Baipiaoji (baipiaoji.com)".
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of: chat, coding, image, video, audio, design, search, study, office, writing, api, agent, local, safety |
| fully_free | boolean | – | Only tools that are entirely free |
| lang | string | – | Data language, default en |
| query | string | – | Keyword to match against name/tagline/tags |
| tag | string | – | Match a capability tag, e.g. "No signup", "Runs locally", "Open source", "Free API", "Daily credits", "Commercial use OK", "Self-hostable" |
| works_in_china | boolean | – | Only tools reachable from mainland China without a VPN |
No output schema declared.
No examples provided.
watch_free_tier_changes Watch free-tier changes (webhook) ~189
Subscribe a webhook to verified free-tier changes. When a watched tool's allowance, wall or commercial terms change (verified daily against official vendor pages), the webhook receives a JSON payload with the changed fields, the current wording, the verification date and the source page. Watching up to 3 tools is free; a Pro license key unlocks watching everything. Registration returns a token — keep it, it is the only way to update or delete the watch.
| Name | Type | Req | Description |
|---|---|---|---|
| hook | string | yes | HTTPS webhook URL (Slack/Discord incoming webhook, n8n, or any endpoint accepting POST) |
| key | string | – | Optional Pro license key (bpj.…) to unlock watching all tools |
| slugs | array | yes | Tool slugs to watch (max 3 on the free tier), e.g. ["kimi","suno","cursor"]. Use search_ai_tools to find slugs. |
No output schema declared.
No examples provided.
What is the io.github.f-tiger/verified-ai-free-tiers MCP server?
io.github.f-tiger/verified-ai-free-tiers is an MCP server listed in the public MCP registry as io.github.f-tiger/verified-ai-free-tiers. Verified AI free-tier limits, quota comparisons, commercial-use verdicts and zero-cost workflows. This page covers its hosted endpoint (https://baipiaoji.com/api/mcp).
Is the io.github.f-tiger/verified-ai-free-tiers MCP server safe to use?
io.github.f-tiger/verified-ai-free-tiers scores 78 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 io.github.f-tiger/verified-ai-free-tiers MCP server expose?
io.github.f-tiger/verified-ai-free-tiers exposes 14 tools: search_ai_tools, get_free_tier_limit, compare_free_tiers, check_free_tier_claim, build_free_workflow, and 9 more. Their descriptions and schemas cost roughly 2,223 tokens of context every time the server is loaded.
Does the io.github.f-tiger/verified-ai-free-tiers MCP server require authentication?
No. We connected to io.github.f-tiger/verified-ai-free-tiers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.f-tiger/verified-ai-free-tiers MCP server still maintained?
io.github.f-tiger/verified-ai-free-tiers is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.