List your agent

Street.co.uk MCP by usefulapi

MCP server · hosted · v1.1.0 · io.usefulapi/street-co-uk
Online · tested 2h agoNEW · 2h agoNew version 55m agoSeen in the registry 10m ago

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

What it does

Street.co.uk MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: resume screening. That makes it a candidate for tasks such as screen job applicants or recruit developers.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.1.0
PriceNot in the registry
First seen25 Oct 2026
Last checked10m ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

  • https://street-co-uk.usefulapi.io/mcp streamable-http

In Claude Code: claude mcp add --transport http street-co-uk-mcp-by-usefulapi https://street-co-uk.usefulapi.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE Street.co.uk MCP by usefulapi answered an MCP connection on 25 Oct 2026 and introduced itself as street-co-uk-mcp 1.0.0 (MCP protocol 2025-06-18).

54 tools offered to AI assistants

  • 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_get_property · One property by UUID, with the related records you ask for in include. GET /properties/{id}.
  • 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_get_person · One person by UUID, with the related records you ask for in include. GET /people/{id}.
  • street_list_vendors · List vendors (people selling a property). Newest first as Street orders them; page with page and page_size. GET /vendors.
  • street_get_vendor · One vendor by UUID, with the related records you ask for in include. GET /vendors/{id}.
  • street_list_landlords · List landlords (people letting a property). Newest first as Street orders them; page with page and page_size. GET /landlords.
  • street_get_landlord · One landlord by UUID, with the related records you ask for in include. GET /landlords/{id}.
  • street_list_tenants · List tenants. Newest first as Street orders them; page with page and page_size. GET /tenants.
  • street_get_tenant · One tenant by UUID, with the related records you ask for in include. GET /tenants/{id}.
  • 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_get_sales_applicant · One sales applicant by UUID, with the related records you ask for in include. GET /sales-applicants/{id}.
Show 42 more
  • 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_get_lettings_applicant · One lettings applicant by UUID, with the related records you ask for in include. GET /lettings-applicants/{id}.
  • 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_get_enquiry · One enquiry by UUID, with the related records you ask for in include. GET /enquiries/{id}.
  • 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_get_viewing · One viewing by UUID, with the related records you ask for in include. GET /viewings/{id}.
  • 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_get_valuation · One valuation by UUID, with the related records you ask for in include. GET /valuations/{id}.
  • 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_get_sale · One sale by UUID, with the related records you ask for in include. GET /sales/{id}.
  • 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_get_sales_offer · One sales offer by UUID, with the related records you ask for in include. GET /sales-offers/{id}.
  • 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_get_lettings_offer · One lettings offer by UUID, with the related records you ask for in include. GET /lettings-offers/{id}.
  • 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_get_tenancy · One tenancy by UUID, with the related records you ask for in include. GET /tenancies/{id}.
  • 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_get_maintenance_job · One maintenance job by UUID, with the related records you ask for in include. GET /maintenance-jobs/{id}.
  • 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_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_branches · List branches (name, address, contact details). Newest first as Street orders them; page with page and page_size. GET /branches.
  • street_get_branch · One branch by UUID, with the related records you ask for in include. GET /branches/{id}.
  • 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_get_user · One user by UUID, with the related records you ask for in include. GET /users/{id}.
  • 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_get_invoice · One invoice by UUID, with the related records you ask for in include. GET /invoices/{id}.
  • 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_get_sales_instruction · One sales instruction by UUID, with the related records you ask for in include. GET /sales-instructions/{id}.
  • 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_get_lettings_instruction · One lettings instruction by UUID, with the related records you ask for in include. GET /lettings-instructions/{id}.
  • 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_get_inspection · One inspection by UUID, with the related records you ask for in include. GET /inspections/{id}.
  • 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_get_interested_applicant · One interested applicant by UUID, with the related records you ask for in include. GET /interested-applicants/{id}.
  • 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_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_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 exa
  • 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_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_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 (em

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Tasks it helps with

Share of each task's required capabilities it covers
Screen job applicants
Resume Screening
50%
Recruit developers
Resume Screening
33%

Similar tools

Listed for the same task: screen job applicants

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version1.1.0DECLAREDSRC-001 Official MCP Registry10m ago
Hosted endpointhttps://street-co-uk.usefulapi.io/mcpDECLAREDSRC-001 Official MCP Registry10m ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry10m ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry10m ago
Websitehttps://usefulapi.io/street-co-uk/DECLAREDSRC-001 Official MCP Registry10m ago
Repositoryhttps://github.com/m190/usefulapi-mcpDECLAREDSRC-001 Official MCP Registry10m ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry10m ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry10m ago

Change history

  • VERSION25 Oct 2026
    1.0.0 → 1.1.0
  • NEW25 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Are you the publisher of Street.co.uk MCP by usefulapi?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedInListed on Electra Index
<a href="https://electraindex.com/mcp/street-co-uk-mcp-by-usefulapi?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/street-co-uk-mcp-by-usefulapi" alt="Listed on Electra Index"></a>

Questions about Street.co.uk MCP by usefulapi

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

Use the hosted endpoint https://street-co-uk.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Street.co.uk MCP by usefulapi offer?

When Electra Index connected on 25 Oct 2026, it listed 54 tools: street_list_properties, street_get_property, street_list_people, street_get_person, street_list_vendors, street_get_vendor, street_list_landlords, street_get_landlord and more. The full list is in "Live check" above.

Is Street.co.uk MCP by usefulapi online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.

What can I use Street.co.uk MCP by usefulapi for?

Based on its description, it is most relevant to: screen job applicants, recruit developers.