Skip to content

TinySearch

v0.3.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 29d Search Engines
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Updates What's new, query, and https://github.com/MarcellM01/TinySearch/pull/14 across a mixed release.

Full changelog

TinySearch v0.3.0

Focused release for agent workflows: read a known URL directly, and fetch the current UTC date/time on demand.

What's new

Direct URL inspection - scrape_url / POST /scrape

When you already have a URL, skip full web search. TinySearch crawls the page, ranks relevant chunks against your query, and returns a URL-grounded prompt in answer.

  • MCP: scrape_url(url, query)
  • HTTP: POST /scrape

By @benmaster82 in #14

Current datetime - get_current_datetime / GET /current_datetime

On-demand UTC clock for time-sensitive or relative-date questions (latest, this year, last month). Works reliably over stdio, where MCP instructions are only sent at initialize.

  • MCP: get_current_datetime() - no parameters
  • HTTP: GET /current_datetime
{ "date_utc": "2026-06-28", "time_utc": "08:10:00" }

By @MarcellM01

MCP tools

| Tool | Use when |
|------|----------|
| get_current_datetime() | You need the current UTC date/time before research |
| research(query) | Open-ended discovery - URL not known yet |
| scrape_url(url, query) | A specific URL is already known |

Upgrade notes

No config changes. Existing research(query) behavior is unchanged.

Full Changelog: https://github.com/MarcellM01/TinySearch/compare/v0.2.1...v0.3.0

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track TinySearch

Get notified when new releases ship.

Sign up free

About TinySearch

All releases →

Beta — feedback welcome: [email protected]