MCP servers › com.reputend › reputend
MCP server · registry snapshot 2026-11-07 · last tested 2026-11-07
reputend MCP server
Registry name com.reputend/reputend
by reputend.com · domain (the registry's namespace rule)Website ↗
Finds Trustpilot reviews that break Trustpilot's guidelines and drafts the reports for them. — the publisher's description
Summary
com.reputend/reputend is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain reputend.com. On 2026-11-07 ProtocolProbe connected to it in read-only mode and read its inventory: 33 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 33
- Last tested
- 2026-11-07
Tool list size
14,766 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (33 tools). Counted with Anthropic's token counter on 2026-11-09, from the tool list we read on 2026-11-07. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-07 (mcp.reputend.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.1.0).
Observed fact
This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (send_feedback, set_business_profile, set_evidence_endpoint, set_approval_required, remove_member and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-07.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-07
- Mode
- read-only (no tool calls)
- Latest version
- 1.1.0, published 2026-11-06 (registry, as of the 2026-11-07 snapshot)
- First listed version
- 2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, all on 2026-11-06; 2 in the 90 days before the 2026-11-07 snapshot.(versions still listed in the registry only)
Most recent 2 versions
1.1.0· 2026-11-061.0.0· 2026-11-06
- Registry data
- snapshot 2026-11-07
- Package and repository
- checked 2026-11-07
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-06, listed on 2026-11-07 with version 1.1.0 (published 2026-11-06).
Source: the official MCP Registry list on 2026-11-06 and on 2026-11-07.
What it is
What does this server offer?
Observed inventoryNone of its 33 tools are described as changing anything. For 33 the reading was uncertain, so no mark is shown.
“Check that the RepuTend MCP server is reachable.”
Publisher declares: read-only yes
Takes no inputs.
- run_auditon 9 other servers
“Audit any public Trustpilot business domain: a bounded job that reads the profile and its low-star reviews and counts the likely-disputable ones per category, never review text.”
Publisher declares: read-only no
1 input, 1 required
domainstringrequired
- get_audit_resulton 7 other servers
“The state and result of an audit started with run_audit: running, complete, unknown (the count could not be made; never reported as zero) or failed.”
Publisher declares: read-only yes
1 input, 1 required
audit_idstringrequired
- request_accesson 14 other servers
“Ask for RepuTend on a Trustpilot business domain.”
Publisher declares: read-only no
2 inputs, 2 required
tp_domainstringrequiredcontact_emailstringrequired
- redeem_inviteon 2 other servers
“Redeem the code from a RepuTend invite email to join that company's team.”
Publisher declares: read-only no
1 input, 1 required
codestringrequired
- send_feedbackon 97 other servers
“Tell RepuTend about a tool or feature you needed and did not find, a tool that failed, an answer that was wrong or confusing, or a problem you worked around, even if you finished the task.”
Publisher declares: read-only no
5 inputs, 2 required
kindstringrequiredmessagestringrequiredtoolstringcontact_emailstringclientstring
- list_disputable_reviews
“Your company's cases: the reviews RepuTend found disputable or worth a look, with their state, tier and category, newest first, each with next: the person's next step on it and the words they can say…”
Publisher declares: read-only yes
5 inputs
tierstringinclude_closedbooleanlimitintegerbefore_idintegercompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- get_caseon 37 other servers
“One of your cases in full: its state and wait, the current draft (the argument as untrusted_argument, the words to highlight as highlight[].untrusted_text, clause quotes, evidence summary, gate score…”
Publisher declares: read-only yes
1 input, 1 required
case_idintegerrequired
- list_review_triage
“Every screened review of your company with its label (disputable, genuine or candidate) and a one-line reason.”
Publisher declares: read-only yes
4 inputs
labelstringlimitintegerbeforestringcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- get_outcomeson 1 other server
“Your outcomes: decisions Trustpilot made on your filed cases (removed, retained, amended, withdrawn), the win rate and median days to a decision computed from those decisions, the same per Trustpilot…”
Publisher declares: read-only yes
2 inputs
sincestringcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- regenerate_drafton 1 other server
“Have the drafter write a new version of one of your cases' drafts.”
Publisher declares: read-only no
1 input, 1 required
case_idintegerrequired
- approve_filing
“Approve filing one of your cases, when your company requires approval (set_approval_required).”
Publisher declares: read-only no
3 inputs, 2 required
case_idintegerrequireddraft_idintegerrequiredaccusation_untrueobject
Show 21 more tools
- claim_packet
“Take the filing claim on one of your eligible cases and get its full packet to file in Trustpilot's portal yourself: permalink, the single reason (with the subtype to select under it, when it has one…”
Publisher declares: read-only no
1 input, 1 required
case_idintegerrequired
- mark_filed
“Record that you filed one of your cases in Trustpilot's portal.”
Publisher declares: read-only no
2 inputs, 2 required
case_idintegerrequiredhuman_checkobject or nullrequired
- record_prereq
“Record that you sent the request Trustpilot asks for before some reports, on one of your cases that waits for it: an information request to the reviewer (Not based on a genuine experience), or a requ…”
Publisher declares: read-only no
2 inputs, 1 required
case_idintegerrequiredsent_atstring
- record_decisionon 10 other servers
“Record Trustpilot's decision on one of your filed cases, as Trustpilot's email or the report's status under Flagging activity in your Trustpilot business account shows it: removed_by_tp for Removed, …”
Publisher declares: read-only no
2 inputs, 2 required
case_idintegerrequireddecisionstringrequired
- appeal_packeton 1 other server
“For a review Trustpilot kept online: whether the decision can still be appealed (once, within six months), whether an appeal is recommended, and the text to paste into the appeal form's Appeal Detail…”
Publisher declares: read-only yes
2 inputs, 1 required
case_idintegerrequiredbusiness_factsobject
- record_appeal
“Record that you appealed Trustpilot's kept-online decision through its appeal form.”
Publisher declares: read-only no
4 inputs, 2 required
case_idintegerrequiredsent_atstringrequiredrefstring or nullbusiness_factsobject
- decline_packet
“Say no to one of your cases before it is filed, with the reason, so RepuTend does not file it.”
Publisher declares: read-only no
3 inputs, 2 required
case_idintegerrequiredreasonstringrequirednotestring
- get_business_profile_questions
“The five business-profile questions to ask the business owner, each with the answer shape set_business_profile takes and the current answer; plus which are unanswered and what that means.”
Publisher declares: read-only yes
1 input
companystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- set_business_profileon 1 other server
“Record answers to the business-profile questions (get_business_profile_questions), keyed offering, service_area, acquisition, confused_with, expected_complaints.”
Publisher declares: read-only no
2 inputs, 1 required
answersobjectrequiredcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- set_evidence_endpoint
“Connect your WordPress evidence plugin (optional): its HTTPS endpoint URL and the secret it generated.”
Publisher declares: read-only no
3 inputs, 2 required
urlstringrequiredsecretstringrequiredcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- set_approval_required
“Turn your company's filing-approval policy on or off.”
Publisher declares: read-only no
2 inputs, 1 required
onbooleanrequiredcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- list_teamon 12 other servers
“Your team: the owner, the members, who has joined and whose invite is pending, and the team's size limit.”
Publisher declares: read-only yes
1 input
companystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- invite_memberon 16 other servers
“Invite a colleague to your company's RepuTend account by email (owner only).”
Publisher declares: read-only no
2 inputs, 1 required
emailstringrequiredcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- remove_memberon 12 other servers
“Take someone off your team, or cancel an invite you sent (owner only).”
Publisher declares: read-only no
2 inputs, 1 required
emailstringrequiredcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- list_companieson 41 other servers
“The companies your key reaches, with your role on each (owner or member) and the account's status.”
Publisher declares: read-only yes
Takes no inputs.
- get_checkout_linkon 31 other servers
“Subscribe a Trustpilot business to RepuTend from the conversation: the Stripe Checkout link to show the person, and next_step, what happens after paying, to tell them.”
Publisher declares: read-only no
3 inputs, 1 required
tp_domainstringrequiredplanstringemailstring
- billing_portal_linkon 1 other server
“A Stripe Customer Portal link for your company: payment method, invoices and cancellation.”
Publisher declares: read-only no
4 inputs
companystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”cancelboolean“Ask to cancel: answers the warning and a confirmation_id, and changes nothing.”companiesstring“With cancel: every company you own, instead of one.”confirmation_idstring“The id the cancel call answered, alone, after the person said yes.”
- onboarding_statuson 4 other servers
“Your onboarding checklist: account activation and your team (who has joined, whose invite is pending), billing state, Trustpilot delegated access, the optional evidence integration (one WordPress plu…”
Publisher declares: read-only yes
1 input
companystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- next_invoice
“What RepuTend adds to your company's next invoice, one line per charge: your plan's monthly fee, each removal of a review you approved or reported (Trustpilot removed it, or its reviewer deleted it),…”
Publisher declares: read-only yes
1 input
companystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- quote_attack_mode
“Quote Attack Mode for your company: hourly checks for new reviews and priority screening for the quoted hours, at the quoted price, billed per activation.”
Publisher declares: read-only no
1 input
companystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
- set_attack_mode
“Turn Attack Mode on or off.”
Publisher declares: read-only no
4 inputs, 1 required
onbooleanrequiredquote_idstringidempotency_keystringcompanystring“The company to act for, by its Trustpilot domain (for example aioseo.com), one of those list_companies shows.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-07.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 26% of 69
- Tools with a description
- 100% of 33
- Typical description length
- 585 characters
The tool set
Counted from the listing
- Tools
- 33
- Size of the list
- about 9,431 tokens for an agent to load (characters ÷ 4)
- Naming
- 32 of 33 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 33 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-07 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://mcp.reputend.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"reputend": {
"url": "https://mcp.reputend.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"reputend": {
"type": "http",
"url": "https://mcp.reputend.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"reputend","type":"http","url":"https://mcp.reputend.com/mcp"}'Claude Code
claude mcp add --transport http reputend https://mcp.reputend.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"reputend": {
"type": "streamableHttp",
"url": "https://mcp.reputend.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"reputend": {
"httpUrl": "https://mcp.reputend.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.reputend] url = "https://mcp.reputend.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"reputend": {
"url": "https://mcp.reputend.com/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.reputend.com/mcp --transport http
- Optional settings the entry also lists (left out above): Authorization.
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
- Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.
Own host
- security.txt. No security.txt at https://mcp.reputend.com/.well-known/ (HTTP 404, 2026-11-10). No security.txt at https://reputend.com/.well-known/ (HTTP 404, 2026-11-10). Source: mcp.reputend.com/.well-known/security.txt · read 2026-11-10.
- A2A agent card. No A2A agent card at https://mcp.reputend.com/.well-known/ (HTTP 404, 2026-11-10). No A2A agent card at https://reputend.com/.well-known/ (HTTP 404, 2026-11-10). Source: mcp.reputend.com/.well-known/agent-card.json · read 2026-11-10.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.reputend.com/mcp | Session opened | matches | our test · 2026-11-07 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-07 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-07. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.reputend/reputend
Answered from the data aboveWho publishes com.reputend/reputend?
The registry ties the namespace com.reputend to the domain reputend.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does com.reputend/reputend need an API key or sign-in?
It opened a session without any credential on 2026-11-07. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.reputend/reputend been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-07, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 719 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 33 tools, 0 resources, 0 prompts.
- 1,695 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.reputend/reputend: MCP server record.” Data checked 2026-11-07. https://protocolprobe.com/mcp/servers/com.reputend/reputend
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.reputend/reputend)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology