Portaur
REMOTE · PORTAUR.COM
Ask Portaur about its services and leave a message or callback request for the team.
Available components
Last scanned (16 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 915 tokens (~114/item across 8 items; 8 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 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.
- 19 Nov 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.
- 17 Nov 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.
- 15 Nov 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.
- 13 Nov 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.
- 11 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.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 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
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://portaur.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=portaur.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 25 Aug 2026 | 25 Feb 2027 | RSA 2048 | SHA256-RSA | fb90b0b9aab9f9fadde9fb719900cda |
| SANs: portaur.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of portaur.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| portaur.com. | DS published | 2371 | 13 | Verified |
| portaur.com. | Verified address RRset verified with the apex keys |
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=31556926; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://challenges.cloudflare.com 'nonce-mHNV1peuRdcWD36hgT_HV_gJ8waFNnjV'; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'self'; form-action 'self' https://accounts.google.com https://login.microsoftonline.com https://github.com; base-uri 'self'; object-src 'none'; frame-src 'self' https://challenges.cloudflare.com |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://portaur.com/mcp | Verified | 200 | |
| http (plaintext) | http://portaur.com/mcp | HTTPS enforced | 301 | https://portaur.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 →
about_portaur About Portaur ~73
Returns facts about Portaur LLC, the company behind portaur.com: who it is, its mission, its founder, how to reach it, and the public pages that say more. Read only. The facts are the ones Portaur publishes on its own site. It never returns prices, client names or anything private.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ask_portaur Ask Portaur a question ~98
Asks Portaur's own assistant one question about Portaur and returns its answer, written from the same facts as the website. Read only: the question is answered once and not kept. Use it for a question the other read tools do not answer. It answers only about Portaur, never gives prices, and has a daily limit; once the limit is reached it says so.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | One question about Portaur. |
No output schema declared.
No examples provided.
contact_options How to reach Portaur ~71
Explains the ways to reach a person at Portaur and what each needs: a written message, a request for a phone call back, or an email. It also explains the confirmation email that follows a request. Read only. Call it before send_message or request_callback to learn what to ask the person for.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services List Portaur services ~54
Lists the services Portaur offers, each with its name, a plain language summary and a fuller description, exactly as portaur.com states them. Read only. It never returns prices; pricing_approach explains how pricing works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pricing_approach How Portaur prices work ~46
Explains how Portaur prices its work. Read only. It returns no figures: Portaur never quotes a price through an assistant, and every project is scoped with a person.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_callback Ask Portaur to call back ~222
Asks a person at Portaur to telephone the person you are helping. Needs their name, email address, phone number and the reason for the call; a preferred time window is optional. Use it only when the person asked to be called. It stores the request in Portaur's inbox and sends one email to the address given, asking the person to confirm; Portaur's phone is alerted only after they do. A person makes the call by hand: nothing ever dials or texts the number. Returns a handle for request_status. It never sends anything to anyone else and never quotes a price.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Their email address. Portaur sends one confirmation email here. | |
| name | string | yes | The name of the person who wants a call. |
| phone | string | yes | The number to call: 7 to 15 digits, with spaces and + ( ) . allowed. |
| reason | string | yes | What the call is about. |
| window | string | – | When they would like the call, with their time zone. Optional. |
No output schema declared.
No examples provided.
request_status Check a request ~77
Says how a request made with send_message or request_callback is doing, given the handle that tool returned: waiting for the person to confirm their email, confirmed and the owner has been told, or not found. Read only. It never returns the message or the address.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The handle send_message or request_callback returned. |
No output schema declared.
No examples provided.
send_message Leave a message for Portaur ~176
Leaves a written message for a person at Portaur on behalf of the person you are helping. Needs their name, their email address and the message; a subject is optional. Use it only when the person asked you to contact Portaur. It stores the message in Portaur's inbox and sends one email to the address given, asking the person to confirm; nothing reaches a person's phone until they do. Returns a handle for request_status. It never sends anything to anyone else, never calls or texts anyone, and never quotes a price.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The message, in their words. |
| string | yes | Their email address. Portaur sends one confirmation email here. | |
| name | string | yes | The name of the person you are writing for. |
| subject | string | – | A short subject line. Optional. |
No output schema declared.
No examples provided.
How do I install the Portaur MCP server?
Portaur is a hosted endpoint at https://portaur.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 · portaur.com
claude mcp add --transport http com-portaur-portaur 'https://portaur.com/mcp'
What is the Portaur MCP server?
Portaur is an MCP server listed in the public MCP registry as com.portaur/portaur. Ask Portaur about its services and leave a message or callback request for the team. This page covers its hosted endpoint (https://portaur.com/mcp).
Is the Portaur MCP server safe to use?
Portaur scores 86 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 Portaur MCP server expose?
Portaur exposes 8 tools: about_portaur, list_services, contact_options, pricing_approach, ask_portaur, and 3 more. Their descriptions and schemas cost roughly 817 tokens of context every time the server is loaded.
Does the Portaur MCP server require authentication?
No. We connected to Portaur without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Portaur MCP server still maintained?
Portaur 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 Portaur MCP server?
VerifyMCP ran 13 checks on Portaur, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.