Agent-accessible map of global supply & demand: jobs, homes, cars & services your AI can act on
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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. Publishing consumes credits and requires a free listing slot; get_entitlements reports the current balance and remaining slots. A reached limit makes this return an ACTIVE_LISTING_LIMIT_REACHED error carrying a pay_url. 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. Requires the user to be connected to Teppek: an anonymous call returns an AUTH_REQUIRED error with an authorize_url — surface "Connect with Teppek" to the user, then retry.
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 vehicle_renter. Likewise estate_landlord (renting out) vs estate_renter (wants to rent), estate_seller vs estate_buyer, career_employer (posting a job) vs career_seeker (a CV), service_pro (offering) vs service_client (wants a service).
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.
Listing coordinates as { lat, lon }. A free-text address is NOT accepted — resolve it to coordinates before calling.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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. Publishing consumes credits and requires a free listing slot; get_entitlements reports the current balance and remaining slots. A reached limit makes this return an ACTIVE_LISTING_LIMIT_REACHED error carrying a pay_url. 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. Requires the user to be connected to Teppek: an anonymous call returns an AUTH_REQUIRED error with an authorize_url — surface "Connect with Teppek" to the user, then retry.
| Argument | Type | Description |
|---|---|---|
| role* | string | 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 vehicle_renter. Likewise estate_landlord (renting out) vs estate_renter (wants to rent), estate_seller vs estate_buyer, career_employer (posting a job) vs career_seeker (a CV), service_pro (offering) vs service_client (wants a service). |
| price* | number | |
| title* | string | |
| images | array | |
| details | object | |
| currency* | string | 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. |
| location* | object | Listing coordinates as { lat, lon }. A free-text address is NOT accepted — resolve it to coordinates before calling. |
| vertical* | string | |
| description | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"vertical",
"role",
"title",
"price",
"currency",
"location"
],
"properties": {
"role": {
"enum": [
"career_employer",
"career_seeker",
"estate_buyer",
"estate_landlord",
"estate_renter",
"estate_seller",
"service_client",
"service_pro",
"vehicle_buyer",
"vehicle_letter",
"vehicle_renter",
"vehicle_seller"
],
"type": "string",
"description": "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 vehicle_renter. Likewise estate_landlord (renting out) vs estate_renter (wants to rent), estate_seller vs estate_buyer, career_employer (posting a job) vs career_seeker (a CV), service_pro (offering) vs service_client (wants a service)."
},
"price": {
"type": "number",
"minimum": 0
},
"title": {
"type": "string",
"maxLength": 200,
"minLength": 3
},
"images": {
"type": "array",
"items": {
"type": "string",
"maxLength": 512,
"minLength": 1
},
"maxItems": 6
},
"details": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
}
]
}
},
"currency": {
"type": "string",
"maxLength": 8,
"minLength": 1,
"description": "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."
},
"location": {
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number",
"maximum": 90,
"minimum": -90
},
"lon": {
"type": "number",
"maximum": 180,
"minimum": -180
}
},
"description": "Listing coordinates as { lat, lon }. A free-text address is NOT accepted — resolve it to coordinates before calling.",
"additionalProperties": false
},
"vertical": {
"enum": [
"career",
"real_estate",
"vehicle",
"service"
],
"type": "string"
},
"description": {
"type": "string",
"maxLength": 5000
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| listing_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"listing_id"
],
"properties": {
"listing_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| thread_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"thread_id"
],
"properties": {
"thread_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}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).
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| listing_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"listing_id"
],
"properties": {
"listing_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| offset | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1
},
"offset": {
"type": "integer",
"default": 0,
"maximum": 9007199254740991,
"minimum": 0
}
}
}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.
| Argument | Type | 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. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1
},
"offset": {
"type": "integer",
"default": 0,
"maximum": 9007199254740991,
"minimum": 0
},
"status": {
"enum": [
"active",
"pending",
"rejected",
"draft",
"sold",
"expired",
"hidden",
"all"
],
"type": "string",
"default": "all",
"description": "Filter YOUR listings by moderation/lifecycle status. Use \"pending\" to see what is awaiting AI moderation, \"rejected\" for declined ones, \"all\" (default) for everything."
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| listing_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"listing_id"
],
"properties": {
"listing_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}Continue an EXISTING message thread by thread_id — the message goes to the other participant. Use this to follow up in a conversation that already exists, whether the user is the listing owner answering an inquiry or the inquirer following up. For the FIRST message to a listing found in search (you have a listing_id but no thread yet), use send_message instead. Contact routes through Teppek; raw personal details are never exposed. Find thread_id via list_conversations / get_conversation.
| Argument | Type | Description |
|---|---|---|
| body* | string | The reply to post into the conversation. Contact routes through Teppek; raw personal details are never exposed. |
| thread_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"thread_id",
"body"
],
"properties": {
"body": {
"type": "string",
"maxLength": 2000,
"minLength": 1,
"description": "The reply to post into the conversation. Contact routes through Teppek; raw personal details are never exposed."
},
"thread_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| file_size* | integer | |
| content_type* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"content_type",
"file_size"
],
"properties": {
"file_size": {
"type": "integer",
"maximum": 10485760,
"exclusiveMinimum": 0
},
"content_type": {
"enum": [
"image/jpeg",
"image/png",
"image/webp",
"image/avif"
],
"type": "string"
}
}
}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. For MEANING-based or fuzzy natural-language intent (not exact keywords or filters), use semantic_search instead. 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.
| Argument | Type | Description |
|---|---|---|
| near | object | |
| 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_employer" instead searches candidate/CV listings. Likewise: estate_buyer → properties for sale, estate_renter → rentals, vehicle_buyer → vehicles for sale, vehicle_renter → vehicles for rent, service_client → service providers. Pair with text_query and/or near. |
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.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| query* | string | 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 keywords. |
| vertical | string | Optional vertical filter (career | real_estate | vehicle | service) applied server-side to the active listings before they are returned. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 20,
"maximum": 20,
"minimum": 1
},
"query": {
"type": "string",
"maxLength": 200,
"minLength": 2,
"description": "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 keywords."
},
"vertical": {
"enum": [
"career",
"real_estate",
"vehicle",
"service"
],
"type": "string",
"description": "Optional vertical filter (career | real_estate | vehicle | service) applied server-side to the active listings before they are returned."
}
}
}START contact with the owner of a Teppek LISTING on the user's behalf (identified by the listing) — the primary FIRST-CONTACT path (there is no price-offer/accept/reject flow). Opens a private thread with the owner; contact routes through Teppek and never exposes raw personal details. To continue a thread that already EXISTS (you have a thread_id from list_conversations), use reply_to_conversation instead. 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. Requires the user to be connected to Teppek: an anonymous call returns an AUTH_REQUIRED error with an authorize_url — surface 'Connect with Teppek' to the user, then retry.
| Argument | Type | Description |
|---|---|---|
| body* | string | The message to send to the listing owner. Contact routes through Teppek; raw personal details are never exposed. |
| listing_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"listing_id",
"body"
],
"properties": {
"body": {
"type": "string",
"maxLength": 2000,
"minLength": 1,
"description": "The message to send to the listing owner. Contact routes through Teppek; raw personal details are never exposed."
},
"listing_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| status* | string | 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 moderation states. |
| listing_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"listing_id",
"status"
],
"properties": {
"status": {
"enum": [
"active",
"hidden",
"sold"
],
"type": "string",
"description": "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 moderation states."
},
"listing_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| price | number | |
| title | string | |
| details | object | |
| currency | string | |
| location | object | New listing coordinates { lat, lon }. Moving a listing re-triggers AI moderation — it returns to "pending" until cleared. |
| listing_id* | string | |
| description | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"listing_id"
],
"properties": {
"price": {
"type": "number",
"minimum": 0
},
"title": {
"type": "string",
"maxLength": 200,
"minLength": 3
},
"details": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
}
]
}
},
"currency": {
"type": "string",
"maxLength": 8,
"minLength": 1
},
"location": {
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number",
"maximum": 90,
"minimum": -90
},
"lon": {
"type": "number",
"maximum": 180,
"minimum": -180
}
},
"description": "New listing coordinates { lat, lon }. Moving a listing re-triggers AI moderation — it returns to \"pending\" until cleared.",
"additionalProperties": false
},
"listing_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"description": {
"type": "string",
"maxLength": 5000
}
}
}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).
| Argument | Type | 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 on a listing. |
| remove | array | Image keys currently on the listing to detach. |
| listing_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"listing_id"
],
"properties": {
"add": {
"type": "array",
"items": {
"type": "string",
"maxLength": 512,
"minLength": 1
},
"maxItems": 6,
"description": "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 on a listing."
},
"remove": {
"type": "array",
"items": {
"type": "string",
"maxLength": 512,
"minLength": 1
},
"maxItems": 6,
"description": "Image keys currently on the listing to detach."
},
"listing_id": {
"type": "string",
"maxLength": 64,
"minLength": 1
}
}
}| limit |
| integer |
| offset | integer |
| 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:"us" + text_query:"waiter"); use country alone (no text_query) to get the total number of listings in that country. |
| 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 sort, so scope by vertical/country when mixing currencies. |
| 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 text_query for counting an occupation. With no text_query, the response meta.total is the exact count for that category (optionally + country), and meta.categories lists the available category slugs with counts — call once with country alone to discover them. |
| vertical | string |
| 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 response cannot apply it, price_min is listed in meta.ignored_filters. |
| text_query | string |
| intent_type | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"near": {
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number",
"maximum": 90,
"minimum": -90
},
"lon": {
"type": "number",
"maximum": 180,
"minimum": -180
},
"radius_km": {
"type": "number",
"default": 10,
"maximum": 200,
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"role": {
"enum": [
"career_employer",
"career_seeker",
"estate_buyer",
"estate_landlord",
"estate_renter",
"estate_seller",
"service_client",
"service_pro",
"vehicle_buyer",
"vehicle_letter",
"vehicle_renter",
"vehicle_seller"
],
"type": "string",
"description": "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_employer\" instead searches candidate/CV listings. Likewise: estate_buyer → properties for sale, estate_renter → rentals, vehicle_buyer → vehicles for sale, vehicle_renter → vehicles for rent, service_client → service providers. Pair with text_query and/or near."
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1
},
"offset": {
"type": "integer",
"default": 0,
"maximum": 9007199254740991,
"minimum": 0
},
"country": {
"type": "string",
"maxLength": 2,
"minLength": 2,
"description": "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:\"us\" + text_query:\"waiter\"); use country alone (no text_query) to get the total number of listings in that country."
},
"sort_by": {
"enum": [
"price_asc",
"price_desc"
],
"type": "string",
"description": "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 sort, so scope by vertical/country when mixing currencies."
},
"category": {
"type": "string",
"maxLength": 64,
"minLength": 2,
"description": "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 text_query for counting an occupation. With no text_query, the response meta.total is the exact count for that category (optionally + country), and meta.categories lists the available category slugs with counts — call once with country alone to discover them."
},
"vertical": {
"enum": [
"career",
"real_estate",
"vehicle",
"service"
],
"type": "string"
},
"price_max": {
"type": "number",
"minimum": 0,
"description": "Maximum price/salary. Currency-naive raw-number compare (see price_min). If unapplied it appears in meta.ignored_filters."
},
"price_min": {
"type": "number",
"minimum": 0,
"description": "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 response cannot apply it, price_min is listed in meta.ignored_filters."
},
"text_query": {
"type": "string",
"maxLength": 200,
"minLength": 1
},
"intent_type": {
"enum": [
"supply",
"demand"
],
"type": "string"
}
}
}