Street.co.uk MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Street.co.uk MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 54 tools. Last commit 1 Nov 2026.

Read Street.co.uk properties, applicants, viewings, tenancies, jobs; create enquiries, notes, tasks.

Uptime history 7 days of history · worst day 99%

7 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

167 ms

Response time

average over 24h

Stars

last commit 1 Nov 2026

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 October 2026. No other catalogue keeps this.

31 Oct a tool changed version4 times that day

30 Oct a tool changed version2 times that day

29 Oct a tool changed version2 times that day

28 Oct a tool changed version

27 Oct a tool changed version

and 5 more, back to 27 October 2026

Street.co.uk MCP by usefulapi missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add street-co-uk --transport http https://street-co-uk.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://street-co-uk.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.street-co-uk]
url = "https://street-co-uk.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "street-co-uk": {
      "url": "https://street-co-uk.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "street-co-uk": {
      "type": "http",
      "url": "https://street-co-uk.usefulapi.io/mcp"
    }
  }
}

Available tools 54

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

street

street_create_enquiry

WRITE: record a new inbound enquiry (a lead) in Street. Street matches the email address to an existing person or creates one, and the agency's own automations may then email or assign the lead. Street requires the enquiry to be tied to exactly one record: pass property_id, or sales_applicant_id, or lettings_applicant_id. Pass the same enquiry_identifier on a retry: Street then returns the existing enquiry instead of creating a duplicate. POST /enquiries.

street_create_follow_up

WRITE: schedule a follow-up on a property, sales or lettings applicant, sale or valuation. Not idempotent: calling it twice creates two follow-ups. POST /follow-ups.

street_create_maintenance_request

WRITE: log a maintenance request against a property (a request, not a job: Street staff turn it into a job). Not idempotent: calling it twice logs two requests. POST /maintenance-requests.

street_create_note

WRITE: add a note to one Street record (a person, property, applicant, sale, viewing, tenancy and so on). The note is visible to the agency's staff. Not idempotent: calling it twice adds two notes. POST /notes.

street_create_task

WRITE: create a task (to-do) in Street, optionally assigned to a user and given a task type. Not idempotent: calling it twice creates two tasks. POST /todos.

street_get_branch

One branch by UUID, with the related records you ask for in include. GET /branches/{id}.

street_get_enquiry

One enquiry by UUID, with the related records you ask for in include. GET /enquiries/{id}.

street_get_inspection

One inspection by UUID, with the related records you ask for in include. GET /inspections/{id}.

street_get_interested_applicant

One interested applicant by UUID, with the related records you ask for in include. GET /interested-applicants/{id}.

street_get_invoice

One invoice by UUID, with the related records you ask for in include. GET /invoices/{id}.

street_get_landlord

One landlord by UUID, with the related records you ask for in include. GET /landlords/{id}.

street_get_lettings_applicant

One lettings applicant by UUID, with the related records you ask for in include. GET /lettings-applicants/{id}.

street_get_lettings_instruction

One lettings instruction by UUID, with the related records you ask for in include. GET /lettings-instructions/{id}.

street_get_lettings_offer

One lettings offer by UUID, with the related records you ask for in include. GET /lettings-offers/{id}.

street_get_maintenance_job

One maintenance job by UUID, with the related records you ask for in include. GET /maintenance-jobs/{id}.

street_get_person

One person by UUID, with the related records you ask for in include. GET /people/{id}.

street_get_property

One property by UUID, with the related records you ask for in include. GET /properties/{id}.

street_get_sale

One sale by UUID, with the related records you ask for in include. GET /sales/{id}.

street_get_sales_applicant

One sales applicant by UUID, with the related records you ask for in include. GET /sales-applicants/{id}.

street_get_sales_instruction

One sales instruction by UUID, with the related records you ask for in include. GET /sales-instructions/{id}.

street_get_sales_offer

One sales offer by UUID, with the related records you ask for in include. GET /sales-offers/{id}.

street_get_tenancy

One tenancy by UUID, with the related records you ask for in include. GET /tenancies/{id}.

street_get_tenant

One tenant by UUID, with the related records you ask for in include. GET /tenants/{id}.

street_get_user

One user by UUID, with the related records you ask for in include. GET /users/{id}.

street_get_valuation

One valuation by UUID, with the related records you ask for in include. GET /valuations/{id}.

street_get_vendor

One vendor by UUID, with the related records you ask for in include. GET /vendors/{id}.

street_get_viewing

One viewing by UUID, with the related records you ask for in include. GET /viewings/{id}.

street_list_areas

List areas (the area names used to match applicants and properties). Newest first as Street orders them; page with page and page_size. GET /areas.

street_list_branches

List branches (name, address, contact details). Newest first as Street orders them; page with page and page_size. GET /branches.

street_list_enquiries

List enquiries (inbound leads: who, which property, message, source). Newest first as Street orders them; page with page and page_size. GET /enquiries.

street_list_follow_ups

List follow-ups (due date, note, and the property, applicant, sale or valuation they belong to). Newest first as Street orders them; page with page and page_size. GET /follow-ups.

street_list_inspections

List property inspections (due date, booked date, inspector, status). Newest first as Street orders them; page with page and page_size. GET /inspections.

street_list_interested_applicants

List interested applicants (applicants who showed interest in a property). Newest first as Street orders them; page with page and page_size. GET /interested-applicants.

street_list_invoices

List invoices (client accounting: property, owner, line items, paid and voided state). Newest first as Street orders them; page with page and page_size. GET /invoices.

street_list_landlords

List landlords (people letting a property). Newest first as Street orders them; page with page and page_size. GET /landlords.

street_list_lettings_applicants

List lettings applicants (prospective tenants: budget, bedrooms, areas, furnished, lead rating). Newest first as Street orders them; page with page and page_size. GET /lettings-applicants.

street_list_lettings_instructions

List lettings instructions (an agreement to let: property, owner). Newest first as Street orders them; page with page and page_size. GET /lettings-instructions.

street_list_lettings_offers

List lettings offers (rent, applicant, property, status). Newest first as Street orders them; page with page and page_size. GET /lettings-offers.

street_list_maintenance_jobs

List maintenance jobs (read-only: property, status, assignee, dates). Newest first as Street orders them; page with page and page_size. GET /maintenance-jobs.

street_list_people

List people (contacts: name, emails, phones, addresses, contact preferences). Newest first as Street orders them; page with page and page_size. GET /people.

street_list_properties

List properties (sales and lettings listings, with address, status, price, bedrooms and the owner link). Newest first as Street orders them; page with page and page_size. GET /properties.

street_list_sales

List sales (the sales progression records: agreed price, buyer, vendor, solicitors, status). Newest first as Street orders them; page with page and page_size. GET /sales.

street_list_sales_applicants

List sales applicants (buyers: budget, bedrooms, areas, buying and financial position, lead rating). Newest first as Street orders them; page with page and page_size. GET /sales-applicants.

street_list_sales_instructions

List sales instructions (an agreement to sell: property, owner, fees). Newest first as Street orders them; page with page and page_size. GET /sales-instructions.

street_list_sales_offers

List sales offers (amount, applicant, property, status). Newest first as Street orders them; page with page and page_size. GET /sales-offers.

street_list_task_types

List task types (the categories a task can have; use an id as task_type_id when creating a task). Newest first as Street orders them; page with page and page_size. GET /todo-types.

street_list_tasks

List tasks (to-dos with title, due date, assignee and the record they relate to). Newest first as Street orders them; page with page and page_size. GET /todos.

street_list_tenancies

List tenancies (property, tenants, owner, rent, dates). Newest first as Street orders them; page with page and page_size. GET /tenancies.

street_list_tenants

List tenants. Newest first as Street orders them; page with page and page_size. GET /tenants.

street_list_users

List users (the agency's staff: name, job title, contact details, deactivated state). Newest first as Street orders them; page with page and page_size. GET /users.

street_list_valuations

List valuations (market appraisals: property, valuer, time, status, outcome). Newest first as Street orders them; page with page and page_size. GET /valuations.

street_list_vendors

List vendors (people selling a property). Newest first as Street orders them; page with page and page_size. GET /vendors.

street_list_viewings

List viewings (property, applicant, time, status, feedback). Newest first as Street orders them; page with page and page_size. GET /viewings.

street_update_person

WRITE: change a person's title, name, marketing consent or contact preferences in Street. Street requires both names on every update, so the current record is read first and anything you leave out is sent back unchanged. Contact details (email, phone, address) cannot be changed through the API. PATCH /people/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://street-co-uk.usefulapi.io/mcp	streamable-http	answering	164 ms	12 min ago

Alternatives to Street.co.uk MCP by usefulapi

same job, measured the same way

DoorLoop MCP by usefulapi

by usefulapi

Read DoorLoop properties, units, leases, tenants and payments; create tasks and task updates.

21 tools answering

Rex Software MCP by usefulapi

by usefulapi

Read contacts, listings, tenancies and tasks; create a person contact, note or reminder.

33 tools answering

Arthur Online MCP by usefulapi

by usefulapi

Read Arthur properties, units and tenancies; track maintenance and add tasks or notes.

20 tools answering

Propstack MCP by usefulapi

by usefulapi

Read Propstack contacts, properties, projects, deals, tasks, events; create and update CRM records.

18 tools answering

Propertyware MCP by usefulapi

by usefulapi

Read Propertyware properties, leases and work orders; add maintenance tasks and comments.

21 tools answering

Homerun MCP by usefulapi

by usefulapi

Read Homerun vacancies, applications, notes and tags; move an application to a stage or add a note.

9 tools answering

Semble MCP by usefulapi

by usefulapi

Read Semble patients, bookings, invoices and products; create patients and tasks, label patients.

19 tools answering

Kickserv MCP by usefulapi

by usefulapi

Look up Kickserv customers, jobs, notes and time entries, and create jobs, tasks and charges.

20 tools answering

Street.co.uk MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Street.co.uk MCP by usefulapi do?

It exposes 54 tools, read directly from the server on our last check. Among them: street_create_enquiry, street_create_follow_up, street_create_maintenance_request, street_create_note, street_create_task, street_get_branch and 48 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Street.co.uk MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 167 ms. The bar chart above shows every period we have measured.

How do I connect Street.co.uk MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Street.co.uk MCP by usefulapi need an API key?

No. Street.co.uk MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 54 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Street.co.uk MCP by usefulapi?

It answers our handshake in 167 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Street.co.uk MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at street-co-uk.usefulapi.io, which runs on its operator's own terms.