Parlel
REMOTE · API.PARLEL.COM
Search people, companies and open roles on Parlel, an open professional network.
Available components
Last scanned (21 hours ago)
Scores higher than 67% 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 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 8 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 885 tokens (~98/item across 9 items; 8 tools + 1 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_person” rewrote its description, which is the text the model reads security
- Tool “search_people” rewrote its description, which is the text the model reads security
- Schema quality: 87 → 98 ▼ functional
- 9 Oct 26 0
- Stability: 0.90 → pass security
- 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
- 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
- 10 Sept 26 0
- Stability: unverified → 0.03 ▲ 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://api.parlel.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=parlel.com | CN=YR1,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 54eb8b6956bf2f7219ffb272d3b88b3cec0 |
| SANs: api.parlel.com, parlel.com, www.parlel.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.parlel.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| parlel.com. | No DS | 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.parlel.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.parlel.com/mcp | HTTPS enforced | 301 | https://api.parlel.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 →
get_agent Read one agent and its findings ~31
One published agent by slug: its brief, schedule and recent findings with sources.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_company Read one company ~26
One company by handle, with its open roles inline.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_job Read one role ~44
One role by id, with its full description, skills, pay and the hiring company. Works for closed roles too; read `status`.
| Name | Type | Req | Description |
|---|---|---|---|
| role_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_person Read one profile ~60
One published profile by handle: headline, bio, work history, education, skills, recent posts and the agents they publish. Free MCP access can read only the fixed 10-profile sample; Pro company keys can read all.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_agents Browse published watch agents ~68
Published watch agents -- standing searches people run against the open web -- with a preview of what each has found. No text filter; walk the list. `sort` is `recent` or `popular`.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| sort | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_companies Search companies ~94
Companies with a published page. `q` matches name, tagline or industry; `industry` is an exact label; `hiring=true` narrows to companies with at least one open role. Each item has `open_role_count`.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| hiring | – | – | – |
| industry | – | – | – |
| limit | integer | – | – |
| location | – | – | – |
| q | – | – | – |
| size | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_jobs Search open roles ~90
Open roles on Parlel, newest first. `q` matches the TITLE only. Filter by working arrangement, seniority and a pay floor. Returns {items, next_cursor}; each item has a `role_url` you can cite.
| Name | Type | Req | Description |
|---|---|---|---|
| comp_min | – | – | – |
| cursor | – | – | – |
| limit | integer | – | – |
| q | – | – | – |
| remote | – | – | – |
| seniority | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_people Search people ~146
Published profiles. `q` matches name, headline, company, role and work history (not skills, not bio). `skills` are exact tags, AND-ed. `based_in` is where the person is; `location` also matches where they would move to. Contact details are never returned. Free access searches the same 10-profile sample; an API key linked to Pro searches all profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| based_in | – | – | – |
| comp_max | – | – | – |
| cursor | – | – | – |
| limit | integer | – | – |
| location | – | – | – |
| open_to_work | – | – | – |
| q | – | – | – |
| remote | – | – | – |
| seniority | – | – | – |
| skills | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Parlel MCP server?
Parlel is a hosted endpoint at https://api.parlel.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 · api.parlel.com
claude mcp add --transport http com-parlel-parlel 'https://api.parlel.com/mcp'
What is the Parlel MCP server?
Parlel is an MCP server listed in the public MCP registry as com.parlel/parlel. Search people, companies and open roles on Parlel, an open professional network. This page covers its hosted endpoint (https://api.parlel.com/mcp).
Is the Parlel MCP server safe to use?
Parlel scores 77 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 Parlel MCP server expose?
Parlel exposes 8 tools: search_jobs, get_job, search_companies, get_company, search_people, and 3 more. Their descriptions and schemas cost roughly 559 tokens of context every time the server is loaded.
Does the Parlel MCP server require authentication?
No. We connected to Parlel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Parlel MCP server still maintained?
Parlel 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 Parlel MCP server?
VerifyMCP ran 12 checks on Parlel, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Parlel: Authorization. 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.