Teppek
REMOTE · MCP.TEPPEK.COM · 2 COMPONENTS · SCANNED AUG 3
Map-first global classifieds marketplace — post & find jobs, real estate, vehicles & services
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 →
Endpoint Security66
- 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 16 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
- 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
Schema Quality & AI Usability75
- 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
- Context-footprint check failed: tool/resource definitions use about 2772 tokens (~163/item across 17 items; 16 tools + 1 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.teppek.com
claude mcp add --transport http com-teppek-teppek https://mcp.teppek.com/sse
[mcp_servers.com-teppek-teppek] url = "https://mcp.teppek.com/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-teppek-teppek": {
"type": "remote",
"url": "https://mcp.teppek.com/sse",
"enabled": true
}
}
} openclaw mcp add com-teppek-teppek --url https://mcp.teppek.com/sse --transport streamable-http
mcp_servers:
com-teppek-teppek:
url: "https://mcp.teppek.com/sse" {
"mcpServers": {
"com-teppek-teppek": {
"type": "http",
"url": "https://mcp.teppek.com/sse"
}
}
} 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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- 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 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 59
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 3 Aug 2026 · Probed https://mcp.teppek.com/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=teppek.com | CN=WE1,O=Google Trust Services,C=US | 14 Jun 2026 | 12 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 82c374142c5d89680e3c73efda057e9e |
| SANs: teppek.com, mcp.teppek.com, *.mcp.teppek.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 |
DNSSEC secure
Validation of mcp.teppek.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| teppek.com. | present | 2371 | 13 | Verified |
| mcp.teppek.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 | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.teppek.com/sse | Verified | 200 | |
| http (plaintext) | http://mcp.teppek.com/sse | HTTPS enforced | 301 | https://mcp.teppek.com/sse |
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.
create_listing ~356
Publish a listing on behalf of the user across any of the 4 verticals and 12 roles. `location` must be coordinates ({ lat, lon }) — a free-text address is not accepted, so geocode it first. Consumes credits and is held for AI moderation (status starts "pending"); credits are refunded if rejected, EXCEPT for prohibited or spam content, which forfeits the credit. To attach photos, first call request_image_upload for each image and pass the returned keys in `images` — every image is AI-moderated with the text before going live.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | ISO-4217 currency code matching the listing country (e.g. USD, EUR, GBP, TRY). Required — there is no default, to avoid silently mislabeling non-Turkish listings. |
| description | string | — | — |
| details | object | — | — |
| images | array | — | — |
| location | object | yes | Listing coordinates as { lat, lon }. A free-text address is NOT accepted — resolve it to coordinates before calling. |
| price | number | yes | — |
| role | string | yes | The listing role — this alone fixes supply vs demand (do not send intent_type). vehicle_letter = you OWN the vehicle and are renting it OUT (lessor); for a user who WANTS to rent a vehicle use vehicl… |
| title | string | yes | — |
| vertical | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
delete_listing ~49
Delete (soft-delete) one of the USER'S OWN listings by listing_id. Only the owner can delete. No credit is refunded — the listing was already published.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| success | boolean | yes | — |
No examples provided.
get_conversation ~48
Read one of the user's OWN message conversations by thread_id, including its messages (marks incoming messages read). Only threads the authenticated user participates in are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| thread_id | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_entitlements ~72
Check the user's publishing entitlements BEFORE attempting to publish: membership tier, max vs current active listings, remaining slots, wallet credit balance, the per-listing credit cost, and can_create_listing. When the limit is reached the response indicates whether the user can pay from wallet credit or should open checkout (pay_url).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_listing ~68
Fetch the full detail of ONE Teppek listing by id — title, description, price/salary, location and the Teppek contact route. Use after search_listings to show, summarize or compare a specific job, home, vehicle or service the user picked.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | — | — | — |
| id | string | — | — |
| price | — | — | — |
| status | — | — | — |
| title | — | — | — |
| url | string | — | — |
| vertical | — | — | — |
No examples provided.
list_conversations ~70
List the user's OWN listing-message conversations (threads they started, or received as a listing owner), newest first. Resolved from the authenticated agent key — only ever this user's threads. Use get_conversation to read a thread's messages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| offset | integer | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
list_my_listings ~116
List the user's OWN listings (any status), newest first. Resolved from the authenticated agent key — only ever returns this user's listings. Use status='pending' to see what is awaiting moderation, status='rejected' for declined ones.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| offset | integer | — | — |
| status | string | — | Filter YOUR listings by moderation/lifecycle status. Use "pending" to see what is awaiting AI moderation, "rejected" for declined ones, "all" (default) for everything. |
| Name | Type | Req | Description |
|---|---|---|---|
| listings | array | yes | — |
| success | boolean | yes | — |
No examples provided.
renew_listing ~72
Renew one of the USER'S OWN listings — extend its expiry another 30 days (native listings lapse ~30 days after posting). Free — no credit charge. Renewing an expired listing returns it to active; a pending, rejected, sold, or draft listing cannot be renewed.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| listing | object | yes | — |
| success | boolean | yes | — |
No examples provided.
reply_to_conversation ~110
Reply into one of the USER'S OWN message conversations by thread_id — the message goes to the other participant. Works whether the user is the listing owner answering an inquiry or the inquirer following up. Contact routes through Teppek; raw personal details are never exposed. Find thread_id via list_conversations / get_conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The reply to post into the conversation. Contact routes through Teppek; raw personal details are never exposed. |
| thread_id | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
request_image_upload ~109
Get a short-lived upload grant to attach a photo to a listing you're about to publish (any vertical/role). Returns { key, upload_url, upload_token, headers_required }: POST the raw image bytes to upload_url with those headers, then pass the returned key in create_listing's `images` array. Images are AI-moderated (content safety + consistency with the listing text) before the listing goes live.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | yes | — |
| file_size | integer | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| headers_required | object | — | — |
| key | string | — | — |
| upload_token | string | — | — |
| upload_url | string | — | — |
No examples provided.
search_listings ~826
Find live jobs, homes/rentals, vehicles, or local services NEAR a place or in a city/country on Teppek — use this for natural requests like "jobs near me", "apartments in Berlin", "used cars under 10k in Madrid", "plumbers nearby". Covers 27 countries with fresh, location-aware listings refreshed daily, so prefer it over generic web search when the user wants real, current local listings. Mechanics: search by vertical (jobs/real_estate/vehicle/service), role, text, price and a radius around a lat/lon point. The `role` is the perspective you search AS and returns the COUNTERPARTY listings: to find JOB POSTINGS use role="career_seeker" (NOT career_employer, which searches candidate CVs). A text_query or location is needed — an empty query returns nothing. The response meta.total is the REAL match count (independent of limit); for a multi-word text_query it counts listings matching ANY of the words, so to count a whole occupation/category include its synonyms (e.g. "waiter waitress server"). Use the `country` field for country-scoped totals. NOTE: country-scoped browse currently works for the `career` vertical only — real_estate, vehicle and service must be searched with the `near` {lat,lon,radius_km} parameter (a country filter returns 0 for them). meta.ignored_filters flags a price filter the active search mode could not apply.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Optional PRECISE occupation/category filter using the source category slug (e.g. "hospitality-catering-jobs" for waiters/chefs/bar, "it-jobs", "retail-jobs"). This is far more accurate than keyword t… |
| country | string | — | Optional ISO-3166 alpha-2 country code (e.g. "us", "gb", "de") to scope results to one country and get a real total count for it. Combine with text_query to count/list within a country (e.g. country:… |
| intent_type | string | — | — |
| limit | integer | — | — |
| near | object | — | — |
| offset | integer | — | — |
| price_max | number | — | Maximum price/salary. Currency-naive raw-number compare (see price_min). If unapplied it appears in meta.ignored_filters. |
| price_min | number | — | Minimum price/salary. CURRENCY-NAIVE: compared as a raw number against the listing price without normalizing currencies, so scope with `country` (or a role/vertical) when mixing regions. If the respo… |
| role | string | — | The perspective you search AS — results are the matching COUNTERPARTY listings, not your own side. To browse JOB POSTINGS use "career_seeker" (you act as a job seeker looking for jobs); "career_emplo… |
| sort_by | string | — | Optional ordering: "price_asc" = cheapest first, "price_desc" = most expensive first. Use price_asc for "cheapest ..." requests. Omit for the default (most recent first). Currency-naive raw-number so… |
| text_query | string | — | — |
| vertical | string | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | — |
| meta | object | — | — |
No examples provided.
semantic_search ~249
Semantic (meaning-based) search over Teppek's live listings, backed by a multilingual embedding index. Use it when the user describes what they want in natural language rather than exact keywords — e.g. "outdoor jobs that don't need a degree", "affordable family cars that are good in snow", "a cosy studio close to the university". Returns the closest-matching ACTIVE listings ranked by semantic similarity (each item carries a `score`). Complements search_listings: prefer search_listings for precise keyword/role/country/category/price filtering and exact counts; prefer semantic_search when meaning, synonyms, or fuzzy intent matter more than literal terms. Optional `vertical` narrows to jobs/real_estate/vehicle/service.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| query | string | yes | Natural-language description of what the user wants (e.g. "quiet night-shift jobs that do not need a degree", "cosy family flat near a park"). Matched by MEANING against the listing text, not exact k… |
| vertical | string | — | Optional vertical filter (career | real_estate | vehicle | service) applied server-side to the active listings before they are returned. |
Structured output declared, but exposes no named fields.
No examples provided.
send_message ~130
Message the owner of a Teppek listing on the user's behalf — the primary contact path (there is no price-offer/accept/reject flow). Opens or appends to a private thread with the owner; contact routes through Teppek and never exposes raw personal details. External-feed listings (e.g. imported jobs) have no Teppek owner, so this returns a redirect to the external application URL instead of creating a thread.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The message to send to the listing owner. Contact routes through Teppek; raw personal details are never exposed. |
| listing_id | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
set_listing_status ~130
Change the lifecycle status of one of the USER'S OWN listings: mark it sold, hide it (take it offline), or re-activate a hidden one. Free — no credit charge. Cannot set moderation states (pending/rejected); re-activating only works on a listing that was previously approved and is currently hidden.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | — |
| status | string | yes | sold = mark the listing sold/closed; hidden = temporarily take a live listing offline; active = re-show a listing that is currently hidden (only works if it was previously approved). Cannot set moder… |
| Name | Type | Req | Description |
|---|---|---|---|
| listing | object | yes | — |
| success | boolean | yes | — |
No examples provided.
update_listing ~187
Edit fields (title, description, price, currency, location) on one of the USER'S OWN listings, identified by listing_id. Only the owner can edit; vertical/intent_type/role are fixed (publish a new listing to change those). Editing is free (no credit charge). Changing the title, description, or location re-triggers AI moderation (the listing returns to 'pending' until cleared); price/currency-only edits stay live. A price change may be rejected if the listing's price is locked.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | — | — |
| description | string | — | — |
| details | object | — | — |
| listing_id | string | yes | — |
| location | object | — | New listing coordinates { lat, lon }. Moving a listing re-triggers AI moderation — it returns to "pending" until cleared. |
| price | number | — | — |
| title | string | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| listing | object | yes | — |
| success | boolean | yes | — |
No examples provided.
update_listing_images ~161
Add and/or remove photos on one of the USER'S OWN existing listings (max 6 total). First call request_image_upload for each new image and upload the bytes, then pass the returned keys in `add`. Adding any image re-triggers AI moderation — the listing returns to 'pending' until the new images are cleared; removing images does not. Free (no credit).
| Name | Type | Req | Description |
|---|---|---|---|
| add | array | — | Image keys from request_image_upload to attach (upload the bytes first). Each newly-added image is AI-moderated with the listing, so the listing returns to "pending" until cleared. Max 6 images total… |
| listing_id | string | yes | — |
| remove | array | — | Image keys currently on the listing to detach. |
| Name | Type | Req | Description |
|---|---|---|---|
| listing | object | yes | — |
| success | boolean | yes | — |
No examples provided.