Fluentive MCP
REMOTE · MCP.FLUENTIVE.APP · SCANNED SEP 22
Information, FAQs, features, and pricing for Fluentive's task management platform.
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 15 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 Usability85
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 900 tokens (~60/item across 15 items; 15 tools + 0 resources), lean.Pass
- 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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 Fluentive MCP server?
Fluentive MCP is a hosted endpoint at https://mcp.fluentive.app/, 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 · mcp.fluentive.app
claude mcp add --transport http app-fluentive-mcp 'https://mcp.fluentive.app/'
{
"mcpServers": {
"app-fluentive-mcp": {
"url": "https://mcp.fluentive.app/"
}
}
} {
"servers": {
"app-fluentive-mcp": {
"type": "http",
"url": "https://mcp.fluentive.app/"
}
}
} [mcp_servers.app-fluentive-mcp] url = "https://mcp.fluentive.app/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-fluentive-mcp": {
"type": "remote",
"url": "https://mcp.fluentive.app/",
"enabled": true
}
}
} openclaw mcp add app-fluentive-mcp --url 'https://mcp.fluentive.app/' --transport streamable-http
mcp_servers:
app-fluentive-mcp:
url: "https://mcp.fluentive.app/" {
"McpServers": {
"app-fluentive-mcp": {
"Transport": "http",
"Url": "https://mcp.fluentive.app/"
}
}
} assistant mcp add app-fluentive-mcp -t streamable-http -u 'https://mcp.fluentive.app/'
{
"mcpServers": {
"app-fluentive-mcp": {
"type": "http",
"url": "https://mcp.fluentive.app/"
}
}
} 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.
- 4 Sept 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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 Jul 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
- 26 Jul 26 0
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 22 Sept 2026 · Probed https://mcp.fluentive.app
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fluentive.app | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | b31536ace6055b3b0e2525859b4fec6c |
| SANs: fluentive.app, *.fluentive.app | ||||||
| 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 mcp.fluentive.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| fluentive.app. | 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://mcp.fluentive.app | Verified | 200 | |
| http (plaintext) | http://mcp.fluentive.app | HTTPS enforced | 301 | https://mcp.fluentive.app/ |
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 →
compare_with_alternatives ~58
Returns a comparison of Fluentive vs common alternatives like Calendly, Google Calendar, HoneyBook, and spreadsheets. Use when the user asks 'Fluentive vs X', why not use a competitor, or needs help choosing a tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_blog_post ~67
Fetches and returns the full text content of a specific Fluentive blog post. Use with URLs returned by list_blog_posts(). The result is cached for 2 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The full URL of the blog post to fetch. Must be a fluentive.app URL. |
No output schema declared.
No examples provided.
get_company_info ~45
Returns information about the company behind Fluentive - team, history, and credibility signals. Use when the user asks who built Fluentive, whether it's trustworthy, or the company's background.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_faq ~44
Returns answers to frequently asked questions about Fluentive - billing, cancellation, data, support, and more. Use when the user has a specific question about how Fluentive works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_features ~48
Returns a full list of Fluentive's features. Use when the user asks what Fluentive can do, whether it has a specific feature like online booking or calendar sync, or wants a feature comparison.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_free_trial_info ~55
Returns details about the Fluentive free trial - duration, requirements, and how to sign up. Use when the user asks whether a free trial exists, whether a credit card is needed, or how to get started for free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_getting_started ~46
Returns a step-by-step guide for getting started with Fluentive. Use when the user wants to know how to start, where to sign up, or what the first steps are.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_onboarding_experience ~45
Returns information about how easy Fluentive is to set up and use. Use when the user asks about difficulty, learning curve, onboarding time, or whether training is needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_overview ~54
Returns a full overview of Fluentive - what it is, who it's for, and its core value proposition. Use when the user asks what Fluentive is, searches for a scheduling or CRM tool, or wants a summary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing ~77
Returns Fluentive's pricing plans - Trial, Single, SmallTeam, and Business - including their contacts and events limits (Trial: up to 5000 contacts / 10000 events; Single, SmallTeam, and Business: unlimited contacts and events). Use when the user asks about cost, plans, or how much Fluentive costs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_security_info ~42
Returns Fluentive's security, privacy, and compliance information. Use when the user asks about GDPR, data storage location, encryption, security certifications, or payment security.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_solution_for_industry ~97
Returns a targeted description of how Fluentive solves problems for a specific industry. Pass the industry name as a parameter (e.g. 'hair salon', 'doctor', 'personal trainer', 'consultant').
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | yes | The industry or profession to get information for. Examples: 'hair salon', 'doctor', 'personal trainer', 'consultant', 'physiotherapist', 'tutor', 'plumber'. |
No output schema declared.
No examples provided.
get_target_audience ~43
Returns a description of who Fluentive is built for - industries, professions, and business types. Use when the user asks if Fluentive fits their profession or business.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_blog_posts ~62
Returns a list of all blog posts published on fluentive.app, fetched live from the sitemap (cached 1 hour). Use when the user asks about recent articles, guides, or tips from Fluentive, or before calling search_content to understand what blog content exists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_content ~117
Searches across ALL Fluentive content — features, pricing, FAQ, comparisons, and live blog posts — for topics relevant to a query. Use for generic questions like 'does Fluentive support X?', 'is it good for Y type of business?', or 'I need software that does Z'. Returns the top 5 most relevant content excerpts.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The topic, question, or feature to search for. Examples: 'online booking', 'team scheduling', 'GDPR compliance', 'hair salon', 'recurring appointments'. |
No output schema declared.
No examples provided.
What is the Fluentive MCP server?
Fluentive MCP is listed in the public MCP registry as app.fluentive/mcp. Information, FAQs, features, and pricing for Fluentive's task management platform. This page covers its hosted endpoint (https://mcp.fluentive.app).
Is the Fluentive MCP server safe to use?
Fluentive MCP scores 80 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 Fluentive MCP server expose?
Fluentive MCP exposes 15 tools: list_blog_posts, get_features, get_blog_post, search_content, get_free_trial_info, and 10 more. Their descriptions and schemas cost roughly 900 tokens of context every time the server is loaded.
Does the Fluentive MCP server require authentication?
No. We connected to Fluentive MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fluentive MCP server still maintained?
Fluentive MCP is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.